Mock Version: 4.1 Mock Version: 4.1 Mock Version: 4.1 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-hyperkitty.spec'], chrootPath='/var/lib/mock/dist-oc9-epol-build-112459-67785/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=991gid=135user='mockbuild'nspawn_args=[]unshare_net=TrueprintOutput=False) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-hyperkitty.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: noarch Building for target noarch Wrote: /builddir/build/SRPMS/python-hyperkitty-1.3.7-1.oc9.src.rpm Child return code was: 0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target noarch --nodeps --nocheck /builddir/build/SPECS/python-hyperkitty.spec'], chrootPath='/var/lib/mock/dist-oc9-epol-build-112459-67785/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=991gid=135user='mockbuild'nspawn_args=[]unshare_net=TrueraiseExc=FalseprintOutput=False) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target noarch --nodeps --nocheck /builddir/build/SPECS/python-hyperkitty.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: noarch Building for target noarch Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.XIcGPA + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf HyperKitty-1.3.7 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/HyperKitty-1.3.7.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd HyperKitty-1.3.7 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/HyperKitty-tox-localdeps.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/HyperKitty-django42-compat.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.Gcq63M + umask 022 + cd /builddir/build/BUILD + cd HyperKitty-1.3.7 + 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 ']' + RPM_TOXENV=py311 + HOSTNAME=rpmbuild + /usr/bin/python3 -s /usr/lib/rpm/OpenCloudOS/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 68.0.0) Handling wheel from default build backend Requirement not satisfied: wheel Exiting dependency generation pass: build backend + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-hyperkitty-1.3.7-1.oc9.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 --noclean --target noarch --nodeps --nocheck /builddir/build/SPECS/python-hyperkitty.spec'], chrootPath='/var/lib/mock/dist-oc9-epol-build-112459-67785/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=991gid=135user='mockbuild'nspawn_args=[]unshare_net=TrueraiseExc=FalseprintOutput=False) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target noarch --nodeps --nocheck /builddir/build/SPECS/python-hyperkitty.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: noarch Building for target noarch Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.XxPhSa + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf HyperKitty-1.3.7 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/HyperKitty-1.3.7.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd HyperKitty-1.3.7 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/HyperKitty-tox-localdeps.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/HyperKitty-django42-compat.patch + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.nYOTeh + umask 022 + cd /builddir/build/BUILD + cd HyperKitty-1.3.7 + 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 ']' + RPM_TOXENV=py311 + HOSTNAME=rpmbuild + /usr/bin/python3 -s /usr/lib/rpm/OpenCloudOS/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 68.0.0) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.41.2) Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.41.2) Handling isort from get_requires_for_build_wheel Requirement not satisfied: isort Exiting dependency generation pass: get_requires_for_build_wheel + RPM_EC=0 ++ jobs -p Wrote: /builddir/build/SRPMS/python-hyperkitty-1.3.7-1.oc9.buildreqs.nosrc.rpm + exit 0 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 --noclean --target noarch --nodeps --nocheck /builddir/build/SPECS/python-hyperkitty.spec'], chrootPath='/var/lib/mock/dist-oc9-epol-build-112459-67785/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=991gid=135user='mockbuild'nspawn_args=[]unshare_net=TrueraiseExc=FalseprintOutput=False) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target noarch --nodeps --nocheck /builddir/build/SPECS/python-hyperkitty.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: noarch Building for target noarch Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.D4Pm5G + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf HyperKitty-1.3.7 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/HyperKitty-1.3.7.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd HyperKitty-1.3.7 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/HyperKitty-tox-localdeps.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/HyperKitty-django42-compat.patch + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.ySdbh8 + umask 022 + cd /builddir/build/BUILD + cd HyperKitty-1.3.7 + 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 ']' + RPM_TOXENV=py311 + HOSTNAME=rpmbuild + /usr/bin/python3 -s /usr/lib/rpm/OpenCloudOS/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 68.0.0) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.41.2) Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.41.2) Handling isort from get_requires_for_build_wheel Requirement satisfied: isort (installed: isort 5.12.0) warning: no files found matching 'requirements.txt' no previously-included directories found matching 'hyperkitty/static/hyperkitty/.sass-cache' warning: no previously-included files found matching 'example_project/settings_local.py' warning: no previously-included files found matching 'example_project/hyperkitty.db' warning: no previously-included files found matching 'example_project/logs/*.log' no previously-included directories found matching 'example_project/static' no previously-included directories found matching 'example_project/fulltext_index' no previously-included directories found matching 'example_project/emails' Handling django <4.3,>=3.2 from wheel metadata: Requires-Dist Requirement not satisfied: django <4.3,>=3.2 Handling django-mailman3 >=1.3.8 from wheel metadata: Requires-Dist Requirement not satisfied: django-mailman3 >=1.3.8 Handling django-gravatar2 >=1.0.6 from wheel metadata: Requires-Dist Requirement not satisfied: django-gravatar2 >=1.0.6 Handling djangorestframework >=3.0.0 from wheel metadata: Requires-Dist Requirement not satisfied: djangorestframework >=3.0.0 Handling robot-detection >=0.3 from wheel metadata: Requires-Dist Requirement not satisfied: robot-detection >=0.3 Handling pytz >=2012 from wheel metadata: Requires-Dist Requirement satisfied: pytz >=2012 (installed: pytz 2022.7.1) Handling django-compressor >=1.3 from wheel metadata: Requires-Dist Requirement not satisfied: django-compressor >=1.3 Handling mailmanclient >=3.3.3 from wheel metadata: Requires-Dist Requirement not satisfied: mailmanclient >=3.3.3 Handling mistune <3.0,>=2.0.0 from wheel metadata: Requires-Dist Requirement not satisfied: mistune <3.0,>=2.0.0 Handling python-dateutil >=2.0 from wheel metadata: Requires-Dist Requirement not satisfied: python-dateutil >=2.0 Handling networkx >=2.0 from wheel metadata: Requires-Dist Requirement not satisfied: networkx >=2.0 Handling django-haystack >=2.8.0 from wheel metadata: Requires-Dist Requirement not satisfied: django-haystack >=2.8.0 Handling django-extensions >=1.3.7 from wheel metadata: Requires-Dist Requirement not satisfied: django-extensions >=1.3.7 Handling flufl.lock >=4.0 from wheel metadata: Requires-Dist Requirement not satisfied: flufl.lock >=4.0 Handling django-q >=1.0.0 from wheel metadata: Requires-Dist Requirement not satisfied: django-q >=1.0.0 Handling Whoosh >=2.5.7 ; extra == 'dev' from wheel metadata: Requires-Dist Ignoring alien requirement: Whoosh >=2.5.7 ; extra == 'dev' Handling django-debug-toolbar ; extra == 'dev' from wheel metadata: Requires-Dist Ignoring alien requirement: django-debug-toolbar ; extra == 'dev' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-hyperkitty-1.3.7-1.oc9.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 --noclean --target noarch --nodeps --nocheck /builddir/build/SPECS/python-hyperkitty.spec'], chrootPath='/var/lib/mock/dist-oc9-epol-build-112459-67785/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=991gid=135user='mockbuild'nspawn_args=[]unshare_net=TrueraiseExc=FalseprintOutput=False) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -br --noclean --target noarch --nodeps --nocheck /builddir/build/SPECS/python-hyperkitty.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: noarch Building for target noarch Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.Isw3xf + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf HyperKitty-1.3.7 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/HyperKitty-1.3.7.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd HyperKitty-1.3.7 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/HyperKitty-tox-localdeps.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + /usr/lib/rpm/rpmuncompress /builddir/build/SOURCES/HyperKitty-django42-compat.patch + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.JAgDSw + umask 022 + cd /builddir/build/BUILD + cd HyperKitty-1.3.7 + 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 ']' + RPM_TOXENV=py311 + HOSTNAME=rpmbuild + /usr/bin/python3 -s /usr/lib/rpm/OpenCloudOS/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 68.0.0) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.41.2) Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.41.2) Handling isort from get_requires_for_build_wheel Requirement satisfied: isort (installed: isort 5.12.0) warning: no files found matching 'requirements.txt' no previously-included directories found matching 'hyperkitty/static/hyperkitty/.sass-cache' warning: no previously-included files found matching 'example_project/settings_local.py' warning: no previously-included files found matching 'example_project/hyperkitty.db' warning: no previously-included files found matching 'example_project/logs/*.log' no previously-included directories found matching 'example_project/static' no previously-included directories found matching 'example_project/fulltext_index' no previously-included directories found matching 'example_project/emails' Handling django <4.3,>=3.2 from wheel metadata: Requires-Dist Requirement satisfied: django <4.3,>=3.2 (installed: django 3.2.24) Handling django-mailman3 >=1.3.8 from wheel metadata: Requires-Dist Requirement satisfied: django-mailman3 >=1.3.8 (installed: django-mailman3 1.3.9) Handling django-gravatar2 >=1.0.6 from wheel metadata: Requires-Dist Requirement satisfied: django-gravatar2 >=1.0.6 (installed: django-gravatar2 1.4.4) Handling djangorestframework >=3.0.0 from wheel metadata: Requires-Dist Requirement satisfied: djangorestframework >=3.0.0 (installed: djangorestframework 3.14.0) Handling robot-detection >=0.3 from wheel metadata: Requires-Dist Requirement satisfied: robot-detection >=0.3 (installed: robot-detection 0.4) Handling pytz >=2012 from wheel metadata: Requires-Dist Requirement satisfied: pytz >=2012 (installed: pytz 2022.7.1) Handling django-compressor >=1.3 from wheel metadata: Requires-Dist Requirement satisfied: django-compressor >=1.3 (installed: django-compressor 4.3.1) Handling mailmanclient >=3.3.3 from wheel metadata: Requires-Dist Requirement satisfied: mailmanclient >=3.3.3 (installed: mailmanclient 3.3.3) Handling mistune <3.0,>=2.0.0 from wheel metadata: Requires-Dist Requirement satisfied: mistune <3.0,>=2.0.0 (installed: mistune 2.0.4) Handling python-dateutil >=2.0 from wheel metadata: Requires-Dist Requirement satisfied: python-dateutil >=2.0 (installed: python-dateutil 2.8.2) Handling networkx >=2.0 from wheel metadata: Requires-Dist Requirement satisfied: networkx >=2.0 (installed: networkx 3.1) Handling django-haystack >=2.8.0 from wheel metadata: Requires-Dist Requirement satisfied: django-haystack >=2.8.0 (installed: django-haystack 3.2.1) Handling django-extensions >=1.3.7 from wheel metadata: Requires-Dist Requirement satisfied: django-extensions >=1.3.7 (installed: django-extensions 3.2.3) Handling flufl.lock >=4.0 from wheel metadata: Requires-Dist Requirement satisfied: flufl.lock >=4.0 (installed: flufl.lock 7.1.1) Handling django-q >=1.0.0 from wheel metadata: Requires-Dist Requirement satisfied: django-q >=1.0.0 (installed: django-q 1.3.9) Handling Whoosh >=2.5.7 ; extra == 'dev' from wheel metadata: Requires-Dist Ignoring alien requirement: Whoosh >=2.5.7 ; extra == 'dev' Handling django-debug-toolbar ; extra == 'dev' from wheel metadata: Requires-Dist Ignoring alien requirement: django-debug-toolbar ; extra == 'dev' + RPM_EC=0 ++ jobs -p + exit 0 Wrote: /builddir/build/SRPMS/python-hyperkitty-1.3.7-1.oc9.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 --nodeps --nocheck /builddir/build/SPECS/python-hyperkitty.spec'], chrootPath='/var/lib/mock/dist-oc9-epol-build-112459-67785/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=86400uid=991gid=135user='mockbuild'nspawn_args=[]unshare_net=TrueprintOutput=False) Executing command: ['bash', '--login', '-c', '/usr/bin/rpmbuild -ba --noprep --noclean --target noarch --nodeps --nocheck /builddir/build/SPECS/python-hyperkitty.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'} and shell False Building target platforms: noarch Building for target noarch Executing(%generate_buildrequires): /bin/sh -e /var/tmp/rpm-tmp.i6RzOB + umask 022 + cd /builddir/build/BUILD + cd HyperKitty-1.3.7 + 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 HyperKitty-1.3.7.dist-info/ removed 'HyperKitty-1.3.7.dist-info/METADATA' removed 'HyperKitty-1.3.7.dist-info/AUTHORS.txt' removed 'HyperKitty-1.3.7.dist-info/COPYING.txt' removed 'HyperKitty-1.3.7.dist-info/top_level.txt' removed directory 'HyperKitty-1.3.7.dist-info/' + '[' -f /usr/bin/python3 ']' + RPM_TOXENV=py311 + HOSTNAME=rpmbuild + /usr/bin/python3 -s /usr/lib/rpm/OpenCloudOS/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 68.0.0) Handling wheel from default build backend Requirement satisfied: wheel (installed: wheel 0.41.2) Handling wheel from get_requires_for_build_wheel Requirement satisfied: wheel (installed: wheel 0.41.2) Handling isort from get_requires_for_build_wheel Requirement satisfied: isort (installed: isort 5.12.0) warning: no files found matching 'requirements.txt' no previously-included directories found matching 'hyperkitty/static/hyperkitty/.sass-cache' warning: no previously-included files found matching 'example_project/settings_local.py' warning: no previously-included files found matching 'example_project/hyperkitty.db' warning: no previously-included files found matching 'example_project/logs/*.log' no previously-included directories found matching 'example_project/static' no previously-included directories found matching 'example_project/fulltext_index' no previously-included directories found matching 'example_project/emails' Handling django <4.3,>=3.2 from wheel metadata: Requires-Dist Requirement satisfied: django <4.3,>=3.2 (installed: django 3.2.24) Handling django-mailman3 >=1.3.8 from wheel metadata: Requires-Dist Requirement satisfied: django-mailman3 >=1.3.8 (installed: django-mailman3 1.3.9) Handling django-gravatar2 >=1.0.6 from wheel metadata: Requires-Dist Requirement satisfied: django-gravatar2 >=1.0.6 (installed: django-gravatar2 1.4.4) Handling djangorestframework >=3.0.0 from wheel metadata: Requires-Dist Requirement satisfied: djangorestframework >=3.0.0 (installed: djangorestframework 3.14.0) Handling robot-detection >=0.3 from wheel metadata: Requires-Dist Requirement satisfied: robot-detection >=0.3 (installed: robot-detection 0.4) Handling pytz >=2012 from wheel metadata: Requires-Dist Requirement satisfied: pytz >=2012 (installed: pytz 2022.7.1) Handling django-compressor >=1.3 from wheel metadata: Requires-Dist Requirement satisfied: django-compressor >=1.3 (installed: django-compressor 4.3.1) Handling mailmanclient >=3.3.3 from wheel metadata: Requires-Dist Requirement satisfied: mailmanclient >=3.3.3 (installed: mailmanclient 3.3.3) Handling mistune <3.0,>=2.0.0 from wheel metadata: Requires-Dist Requirement satisfied: mistune <3.0,>=2.0.0 (installed: mistune 2.0.4) Handling python-dateutil >=2.0 from wheel metadata: Requires-Dist Requirement satisfied: python-dateutil >=2.0 (installed: python-dateutil 2.8.2) Handling networkx >=2.0 from wheel metadata: Requires-Dist Requirement satisfied: networkx >=2.0 (installed: networkx 3.1) Handling django-haystack >=2.8.0 from wheel metadata: Requires-Dist Requirement satisfied: django-haystack >=2.8.0 (installed: django-haystack 3.2.1) Handling django-extensions >=1.3.7 from wheel metadata: Requires-Dist Requirement satisfied: django-extensions >=1.3.7 (installed: django-extensions 3.2.3) Handling flufl.lock >=4.0 from wheel metadata: Requires-Dist Requirement satisfied: flufl.lock >=4.0 (installed: flufl.lock 7.1.1) Handling django-q >=1.0.0 from wheel metadata: Requires-Dist Requirement satisfied: django-q >=1.0.0 (installed: django-q 1.3.9) Handling Whoosh >=2.5.7 ; extra == 'dev' from wheel metadata: Requires-Dist Ignoring alien requirement: Whoosh >=2.5.7 ; extra == 'dev' Handling django-debug-toolbar ; extra == 'dev' from wheel metadata: Requires-Dist Ignoring alien requirement: django-debug-toolbar ; extra == 'dev' + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.qXPEZ6 + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-cc1 -fstack-protector-strong -mbranch-protection=standard -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,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-cc1 -fstack-protector-strong -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-cc1 -fstack-protector-strong -mbranch-protection=standard -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 -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-cc1 -fstack-protector-strong -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules' + export FCFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-ld -Wl,--build-id=sha1' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd HyperKitty-1.3.7 + mkdir -p /builddir/build/BUILD/HyperKitty-1.3.7/.pyproject-builddir + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-cc1 -fstack-protector-strong -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/OpenCloudOS/OpenCloudOS-hardened-ld -Wl,--build-id=sha1' + TMPDIR=/builddir/build/BUILD/HyperKitty-1.3.7/.pyproject-builddir + /usr/bin/python3 -m pip wheel --wheel-dir /builddir/build/BUILD/HyperKitty-1.3.7/pyproject-wheeldir --no-deps --use-pep517 --no-build-isolation --disable-pip-version-check --no-clean --progress-bar off --verbose . Processing /builddir/build/BUILD/HyperKitty-1.3.7 Preparing metadata (pyproject.toml): started Running command Preparing metadata (pyproject.toml) running dist_info creating /builddir/build/BUILD/HyperKitty-1.3.7/.pyproject-builddir/pip-modern-metadata-p_50rjlb/HyperKitty.egg-info writing /builddir/build/BUILD/HyperKitty-1.3.7/.pyproject-builddir/pip-modern-metadata-p_50rjlb/HyperKitty.egg-info/PKG-INFO writing dependency_links to /builddir/build/BUILD/HyperKitty-1.3.7/.pyproject-builddir/pip-modern-metadata-p_50rjlb/HyperKitty.egg-info/dependency_links.txt writing requirements to /builddir/build/BUILD/HyperKitty-1.3.7/.pyproject-builddir/pip-modern-metadata-p_50rjlb/HyperKitty.egg-info/requires.txt writing top-level names to /builddir/build/BUILD/HyperKitty-1.3.7/.pyproject-builddir/pip-modern-metadata-p_50rjlb/HyperKitty.egg-info/top_level.txt writing manifest file '/builddir/build/BUILD/HyperKitty-1.3.7/.pyproject-builddir/pip-modern-metadata-p_50rjlb/HyperKitty.egg-info/SOURCES.txt' reading manifest file '/builddir/build/BUILD/HyperKitty-1.3.7/.pyproject-builddir/pip-modern-metadata-p_50rjlb/HyperKitty.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'requirements.txt' no previously-included directories found matching 'hyperkitty/static/hyperkitty/.sass-cache' warning: no previously-included files found matching 'example_project/settings_local.py' warning: no previously-included files found matching 'example_project/hyperkitty.db' warning: no previously-included files found matching 'example_project/logs/*.log' no previously-included directories found matching 'example_project/static' no previously-included directories found matching 'example_project/fulltext_index' no previously-included directories found matching 'example_project/emails' adding license file 'COPYING.txt' adding license file 'AUTHORS.txt' writing manifest file '/builddir/build/BUILD/HyperKitty-1.3.7/.pyproject-builddir/pip-modern-metadata-p_50rjlb/HyperKitty.egg-info/SOURCES.txt' creating '/builddir/build/BUILD/HyperKitty-1.3.7/.pyproject-builddir/pip-modern-metadata-p_50rjlb/HyperKitty-1.3.7.dist-info' Preparing metadata (pyproject.toml): finished with status 'done' Building wheels for collected packages: HyperKitty Building wheel for HyperKitty (pyproject.toml): started Running command Building wheel for HyperKitty (pyproject.toml) running bdist_wheel running build running build_py creating build creating build/lib creating build/lib/hyperkitty copying hyperkitty/utils.py -> build/lib/hyperkitty copying hyperkitty/feed.py -> build/lib/hyperkitty copying hyperkitty/apps.py -> build/lib/hyperkitty copying hyperkitty/signals.py -> build/lib/hyperkitty copying hyperkitty/__init__.py -> build/lib/hyperkitty copying hyperkitty/forms.py -> build/lib/hyperkitty copying hyperkitty/admin.py -> build/lib/hyperkitty copying hyperkitty/tasks.py -> build/lib/hyperkitty copying hyperkitty/search_indexes.py -> build/lib/hyperkitty copying hyperkitty/urls.py -> build/lib/hyperkitty copying hyperkitty/context_processors.py -> build/lib/hyperkitty copying hyperkitty/checks.py -> build/lib/hyperkitty creating build/lib/hyperkitty/templatetags copying hyperkitty/templatetags/__init__.py -> build/lib/hyperkitty/templatetags copying hyperkitty/templatetags/hk_generic.py -> build/lib/hyperkitty/templatetags copying hyperkitty/templatetags/hk_haystack.py -> build/lib/hyperkitty/templatetags copying hyperkitty/templatetags/decorate.py -> build/lib/hyperkitty/templatetags creating build/lib/hyperkitty/migrations copying hyperkitty/migrations/0002_auto_20150311_0913.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0012_thread_order_null.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0020_auto_20190907_1927.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0004_archived_date_and_subject.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0008_django_mailman3_profile.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0007_allauth_20160808_1604.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/__init__.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0015_mailinglist_id_3.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0023_alter_mailinglist_name.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0021_add_owners_mods.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0005_MailingList_list_id.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0006_thread_on_delete.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0022_mailinglist_archive_rendering_mode.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0016_auto_20180309_0056.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0017_file_attachments.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0010_email_sender_name.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0014_mailinglist_id_2.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0011_email_parent.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0013_mailinglist_id_1.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0018_threadcategory_color.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0003_thread_starting_email.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0009_duplicate_persona_users.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0019_auto_20190127_null_description.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0001_initial.py -> build/lib/hyperkitty/migrations creating build/lib/hyperkitty/models copying hyperkitty/models/email.py -> build/lib/hyperkitty/models copying hyperkitty/models/__init__.py -> build/lib/hyperkitty/models copying hyperkitty/models/vote.py -> build/lib/hyperkitty/models copying hyperkitty/models/mailinglist.py -> build/lib/hyperkitty/models copying hyperkitty/models/category.py -> build/lib/hyperkitty/models copying hyperkitty/models/profile.py -> build/lib/hyperkitty/models copying hyperkitty/models/tag.py -> build/lib/hyperkitty/models copying hyperkitty/models/common.py -> build/lib/hyperkitty/models copying hyperkitty/models/thread.py -> build/lib/hyperkitty/models copying hyperkitty/models/favorite.py -> build/lib/hyperkitty/models copying hyperkitty/models/sender.py -> build/lib/hyperkitty/models creating build/lib/hyperkitty/views copying hyperkitty/views/search.py -> build/lib/hyperkitty/views copying hyperkitty/views/accounts.py -> build/lib/hyperkitty/views copying hyperkitty/views/categories.py -> build/lib/hyperkitty/views copying hyperkitty/views/compat.py -> build/lib/hyperkitty/views copying hyperkitty/views/tags.py -> build/lib/hyperkitty/views copying hyperkitty/views/__init__.py -> build/lib/hyperkitty/views copying hyperkitty/views/mlist.py -> build/lib/hyperkitty/views copying hyperkitty/views/users.py -> build/lib/hyperkitty/views copying hyperkitty/views/message.py -> build/lib/hyperkitty/views copying hyperkitty/views/mailman.py -> build/lib/hyperkitty/views copying hyperkitty/views/index.py -> build/lib/hyperkitty/views copying hyperkitty/views/thread.py -> build/lib/hyperkitty/views creating build/lib/hyperkitty/api copying hyperkitty/api/utils.py -> build/lib/hyperkitty/api copying hyperkitty/api/email.py -> build/lib/hyperkitty/api copying hyperkitty/api/__init__.py -> build/lib/hyperkitty/api copying hyperkitty/api/mailinglist.py -> build/lib/hyperkitty/api copying hyperkitty/api/attachment.py -> build/lib/hyperkitty/api copying hyperkitty/api/tag.py -> build/lib/hyperkitty/api copying hyperkitty/api/thread.py -> build/lib/hyperkitty/api copying hyperkitty/api/sender.py -> build/lib/hyperkitty/api creating build/lib/hyperkitty/tests copying hyperkitty/tests/utils.py -> build/lib/hyperkitty/tests copying hyperkitty/tests/__init__.py -> build/lib/hyperkitty/tests copying hyperkitty/tests/settings_test.py -> build/lib/hyperkitty/tests copying hyperkitty/tests/test_feeds.py -> build/lib/hyperkitty/tests copying hyperkitty/tests/_test_caching.py -> build/lib/hyperkitty/tests copying hyperkitty/tests/test_search_index.py -> build/lib/hyperkitty/tests copying hyperkitty/tests/test_templatetags.py -> build/lib/hyperkitty/tests copying hyperkitty/tests/test_signals.py -> build/lib/hyperkitty/tests copying hyperkitty/tests/test_tasks.py -> build/lib/hyperkitty/tests copying hyperkitty/tests/urls_test.py -> build/lib/hyperkitty/tests creating build/lib/hyperkitty/jobs copying hyperkitty/jobs/update_and_clean_index.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/empty_threads.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/recent_threads_cache.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/orphan_emails.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/__init__.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/thread_starting_email.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/update_index.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/new_lists_from_mailman.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/thread_order_depth.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/sync_mailman.py -> build/lib/hyperkitty/jobs creating build/lib/hyperkitty/management copying hyperkitty/management/utils.py -> build/lib/hyperkitty/management copying hyperkitty/management/__init__.py -> build/lib/hyperkitty/management creating build/lib/hyperkitty/lib copying hyperkitty/lib/view_helpers.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/utils.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/mockup.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/analysis.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/compat.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/__init__.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/incoming.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/user.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/posting.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/mailman.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/renderer.py -> build/lib/hyperkitty/lib creating build/lib/hyperkitty/tests/migrations copying hyperkitty/tests/migrations/__init__.py -> build/lib/hyperkitty/tests/migrations copying hyperkitty/tests/migrations/test_0009.py -> build/lib/hyperkitty/tests/migrations creating build/lib/hyperkitty/tests/models copying hyperkitty/tests/models/__init__.py -> build/lib/hyperkitty/tests/models copying hyperkitty/tests/models/test_tag.py -> build/lib/hyperkitty/tests/models copying hyperkitty/tests/models/test_lastview.py -> build/lib/hyperkitty/tests/models copying hyperkitty/tests/models/test_mailinglist.py -> build/lib/hyperkitty/tests/models copying hyperkitty/tests/models/test_email.py -> build/lib/hyperkitty/tests/models copying hyperkitty/tests/models/test_profile.py -> build/lib/hyperkitty/tests/models copying hyperkitty/tests/models/test_vote.py -> build/lib/hyperkitty/tests/models copying hyperkitty/tests/models/test_sender.py -> build/lib/hyperkitty/tests/models copying hyperkitty/tests/models/test_thread.py -> build/lib/hyperkitty/tests/models creating build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/__init__.py -> build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/test_index.py -> build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/test_search.py -> build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/test_archives.py -> build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/test_mailinglist.py -> build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/test_mailman.py -> build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/test_message.py -> build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/test_compat.py -> build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/test_accounts.py -> build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/test_thread.py -> build/lib/hyperkitty/tests/views creating build/lib/hyperkitty/tests/commands copying hyperkitty/tests/commands/test_attachments_to_file.py -> build/lib/hyperkitty/tests/commands copying hyperkitty/tests/commands/__init__.py -> build/lib/hyperkitty/tests/commands copying hyperkitty/tests/commands/test_import.py -> build/lib/hyperkitty/tests/commands copying hyperkitty/tests/commands/test_mailman_sync.py -> build/lib/hyperkitty/tests/commands creating build/lib/hyperkitty/tests/jobs copying hyperkitty/tests/jobs/__init__.py -> build/lib/hyperkitty/tests/jobs creating build/lib/hyperkitty/tests/lib copying hyperkitty/tests/lib/test_analysis.py -> build/lib/hyperkitty/tests/lib copying hyperkitty/tests/lib/__init__.py -> build/lib/hyperkitty/tests/lib copying hyperkitty/tests/lib/test_incoming.py -> build/lib/hyperkitty/tests/lib copying hyperkitty/tests/lib/test_view_helpers.py -> build/lib/hyperkitty/tests/lib copying hyperkitty/tests/lib/test_mailman.py -> build/lib/hyperkitty/tests/lib copying hyperkitty/tests/lib/test_utils.py -> build/lib/hyperkitty/tests/lib copying hyperkitty/tests/lib/test_posting.py -> build/lib/hyperkitty/tests/lib creating build/lib/hyperkitty/management/commands copying hyperkitty/management/commands/hyperkitty_warm_up_cache.py -> build/lib/hyperkitty/management/commands copying hyperkitty/management/commands/attachments_to_file.py -> build/lib/hyperkitty/management/commands copying hyperkitty/management/commands/__init__.py -> build/lib/hyperkitty/management/commands copying hyperkitty/management/commands/update_index_one_list.py -> build/lib/hyperkitty/management/commands copying hyperkitty/management/commands/mailman_sync.py -> build/lib/hyperkitty/management/commands copying hyperkitty/management/commands/hyperkitty_import.py -> build/lib/hyperkitty/management/commands running egg_info writing HyperKitty.egg-info/PKG-INFO writing dependency_links to HyperKitty.egg-info/dependency_links.txt writing requirements to HyperKitty.egg-info/requires.txt writing top-level names to HyperKitty.egg-info/top_level.txt reading manifest file 'HyperKitty.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no files found matching 'requirements.txt' no previously-included directories found matching 'hyperkitty/static/hyperkitty/.sass-cache' warning: no previously-included files found matching 'example_project/settings_local.py' warning: no previously-included files found matching 'example_project/hyperkitty.db' warning: no previously-included files found matching 'example_project/logs/*.log' no previously-included directories found matching 'example_project/static' no previously-included directories found matching 'example_project/fulltext_index' no previously-included directories found matching 'example_project/emails' adding license file 'COPYING.txt' adding license file 'AUTHORS.txt' writing manifest file 'HyperKitty.egg-info/SOURCES.txt' /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.fixtures' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.fixtures' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.fixtures' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.fixtures' to be distributed and are already explicitly excluding 'hyperkitty.fixtures' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.am.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.am.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.am.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.an.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.an.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ast.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.bem.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.bem.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.bo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.bo.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ce.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ce.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ckb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.co.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.co.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.crh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.crh.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.cv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.cv.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.en_AU.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.en_CA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.en_CA.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.fil.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.fil.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.fo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.fo.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.fr_CA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.fr_CA.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.frp.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.frp.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.fy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.gu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.gu.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ht.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ht.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.hy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.kl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.kl.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ku.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ku.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.kw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.kw.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ky.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.la.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.la.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.lb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.lo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.lo.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.mg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.mg.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.mhr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.mhr.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.mi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.mi.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.mr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ms.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.my.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.nb_NO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.nb_NO.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.nn_NO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.nn_NO.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.oc.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.oc.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.os.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ps.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ps.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.sa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.sa.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.sc.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.sc.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.sd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.sd.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.se.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.se.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.shn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.shn.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.si.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.si.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.szl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.szl.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.tg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ti.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ti.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ug.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.uz.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.wae.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.wae.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.zh_HK.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.zh_HK.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.img' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.js' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.js' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.js' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.js' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.bootstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.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 'hyperkitty.static.hyperkitty.libs.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 'hyperkitty.static.hyperkitty.libs.bootstrap' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.bootstrap.fonts.bootstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.bootstrap.fonts.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 'hyperkitty.static.hyperkitty.libs.bootstrap.fonts.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 'hyperkitty.static.hyperkitty.libs.bootstrap.fonts.bootstrap' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.bootstrap.fonts.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.bootstrap.javascripts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.bootstrap.javascripts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.bootstrap.javascripts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.bootstrap.javascripts' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.bootstrap.javascripts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.mixins' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.mixins' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.mixins' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.mixins' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.mixins' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.utilities' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.utilities' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.utilities' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.utilities' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.utilities' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.vendor' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.vendor' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.vendor' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.vendor' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.vendor' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.fonts.droid' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.fonts.droid' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.fonts.droid' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.fonts.droid' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.fonts.droid' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.fonts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.fonts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.fonts' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.fonts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.fonts.icomoon' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.fonts.icomoon' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.fonts.icomoon' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.fonts.icomoon' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.fonts.icomoon' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.fonts.icomoon.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.fonts.icomoon.fonts' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.fonts.icomoon.fonts' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.fonts.icomoon.fonts' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.fonts.icomoon.fonts' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.jquery' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.jquery' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.jquery' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.jquery' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.jquery' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.jquery.smoothness' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.jquery.smoothness' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.jquery.smoothness' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.jquery.smoothness' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.jquery.smoothness' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.jquery.smoothness.images' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.jquery.smoothness.images' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.jquery.smoothness.images' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.jquery.smoothness.images' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.jquery.smoothness.images' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.mousetrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.mousetrap' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.mousetrap' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.mousetrap' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.mousetrap' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.libs.popper' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.popper' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.popper' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.popper' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.popper' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.sass' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.sass' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.sass' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.sass' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.sass' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.static.hyperkitty.sass.bootstrap' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.sass.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 'hyperkitty.static.hyperkitty.sass.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 'hyperkitty.static.hyperkitty.sass.bootstrap' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.sass.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.templates.account' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.templates.account' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.templates.django_mailman3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.templates.django_mailman3' to be distributed and are already explicitly excluding 'hyperkitty.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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.templates.hyperkitty' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.templates.hyperkitty' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.templates.hyperkitty' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.templates.hyperkitty' to be distributed and are already explicitly excluding 'hyperkitty.templates.hyperkitty' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.templates.hyperkitty.ajax' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.templates.hyperkitty.ajax' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.templates.hyperkitty.ajax' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.templates.hyperkitty.ajax' to be distributed and are already explicitly excluding 'hyperkitty.templates.hyperkitty.ajax' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.templates.hyperkitty.errors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.templates.hyperkitty.errors' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.templates.hyperkitty.errors' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.templates.hyperkitty.errors' to be distributed and are already explicitly excluding 'hyperkitty.templates.hyperkitty.errors' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.templates.hyperkitty.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.templates.hyperkitty.fragments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.templates.hyperkitty.fragments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.templates.hyperkitty.fragments' to be distributed and are already explicitly excluding 'hyperkitty.templates.hyperkitty.fragments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.templates.hyperkitty.messages' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.templates.hyperkitty.messages' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.templates.hyperkitty.messages' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.templates.hyperkitty.messages' to be distributed and are already explicitly excluding 'hyperkitty.templates.hyperkitty.messages' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.templates.hyperkitty.threads' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.templates.hyperkitty.threads' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.templates.hyperkitty.threads' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.templates.hyperkitty.threads' to be distributed and are already explicitly excluding 'hyperkitty.templates.hyperkitty.threads' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.templates.hyperkitty.user_profile' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.templates.hyperkitty.user_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 'hyperkitty.templates.hyperkitty.user_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 'hyperkitty.templates.hyperkitty.user_profile' to be distributed and are already explicitly excluding 'hyperkitty.templates.hyperkitty.user_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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.templates.search.indexes.hyperkitty' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.templates.search.indexes.hyperkitty' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.templates.search.indexes.hyperkitty' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.templates.search.indexes.hyperkitty' to be distributed and are already explicitly excluding 'hyperkitty.templates.search.indexes.hyperkitty' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'hyperkitty.tests.testdata' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.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 'hyperkitty.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 'hyperkitty.tests.testdata' to be distributed and are already explicitly excluding 'hyperkitty.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/hyperkitty/fixtures copying hyperkitty/fixtures/first_start.json -> build/lib/hyperkitty/fixtures copying hyperkitty/fixtures/tag_testdata.json -> build/lib/hyperkitty/fixtures creating build/lib/hyperkitty/locale creating build/lib/hyperkitty/locale/af creating build/lib/hyperkitty/locale/af/LC_MESSAGES copying hyperkitty/locale/af/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/af/LC_MESSAGES creating build/lib/hyperkitty/locale/am creating build/lib/hyperkitty/locale/am/LC_MESSAGES copying hyperkitty/locale/am/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/am/LC_MESSAGES creating build/lib/hyperkitty/locale/an creating build/lib/hyperkitty/locale/an/LC_MESSAGES copying hyperkitty/locale/an/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/an/LC_MESSAGES creating build/lib/hyperkitty/locale/ar creating build/lib/hyperkitty/locale/ar/LC_MESSAGES copying hyperkitty/locale/ar/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ar/LC_MESSAGES creating build/lib/hyperkitty/locale/ast creating build/lib/hyperkitty/locale/ast/LC_MESSAGES copying hyperkitty/locale/ast/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ast/LC_MESSAGES creating build/lib/hyperkitty/locale/az creating build/lib/hyperkitty/locale/az/LC_MESSAGES copying hyperkitty/locale/az/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/az/LC_MESSAGES creating build/lib/hyperkitty/locale/be creating build/lib/hyperkitty/locale/be/LC_MESSAGES copying hyperkitty/locale/be/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/be/LC_MESSAGES creating build/lib/hyperkitty/locale/bem creating build/lib/hyperkitty/locale/bem/LC_MESSAGES copying hyperkitty/locale/bem/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/bem/LC_MESSAGES creating build/lib/hyperkitty/locale/bg creating build/lib/hyperkitty/locale/bg/LC_MESSAGES copying hyperkitty/locale/bg/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/bg/LC_MESSAGES creating build/lib/hyperkitty/locale/bn creating build/lib/hyperkitty/locale/bn/LC_MESSAGES copying hyperkitty/locale/bn/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/bn/LC_MESSAGES creating build/lib/hyperkitty/locale/bo creating build/lib/hyperkitty/locale/bo/LC_MESSAGES copying hyperkitty/locale/bo/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/bo/LC_MESSAGES creating build/lib/hyperkitty/locale/br creating build/lib/hyperkitty/locale/br/LC_MESSAGES copying hyperkitty/locale/br/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/br/LC_MESSAGES creating build/lib/hyperkitty/locale/bs creating build/lib/hyperkitty/locale/bs/LC_MESSAGES copying hyperkitty/locale/bs/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/bs/LC_MESSAGES creating build/lib/hyperkitty/locale/ca creating build/lib/hyperkitty/locale/ca/LC_MESSAGES copying hyperkitty/locale/ca/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ca/LC_MESSAGES creating build/lib/hyperkitty/locale/ca@valencia creating build/lib/hyperkitty/locale/ca@valencia/LC_MESSAGES copying hyperkitty/locale/ca@valencia/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ca@valencia/LC_MESSAGES creating build/lib/hyperkitty/locale/ce creating build/lib/hyperkitty/locale/ce/LC_MESSAGES copying hyperkitty/locale/ce/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ce/LC_MESSAGES creating build/lib/hyperkitty/locale/ckb creating build/lib/hyperkitty/locale/ckb/LC_MESSAGES copying hyperkitty/locale/ckb/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ckb/LC_MESSAGES creating build/lib/hyperkitty/locale/co creating build/lib/hyperkitty/locale/co/LC_MESSAGES copying hyperkitty/locale/co/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/co/LC_MESSAGES creating build/lib/hyperkitty/locale/crh creating build/lib/hyperkitty/locale/crh/LC_MESSAGES copying hyperkitty/locale/crh/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/crh/LC_MESSAGES creating build/lib/hyperkitty/locale/cs creating build/lib/hyperkitty/locale/cs/LC_MESSAGES copying hyperkitty/locale/cs/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/cs/LC_MESSAGES creating build/lib/hyperkitty/locale/cv creating build/lib/hyperkitty/locale/cv/LC_MESSAGES copying hyperkitty/locale/cv/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/cv/LC_MESSAGES creating build/lib/hyperkitty/locale/cy creating build/lib/hyperkitty/locale/cy/LC_MESSAGES copying hyperkitty/locale/cy/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/cy/LC_MESSAGES creating build/lib/hyperkitty/locale/da creating build/lib/hyperkitty/locale/da/LC_MESSAGES copying hyperkitty/locale/da/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/da/LC_MESSAGES creating build/lib/hyperkitty/locale/de creating build/lib/hyperkitty/locale/de/LC_MESSAGES copying hyperkitty/locale/de/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/de/LC_MESSAGES creating build/lib/hyperkitty/locale/el creating build/lib/hyperkitty/locale/el/LC_MESSAGES copying hyperkitty/locale/el/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/el/LC_MESSAGES creating build/lib/hyperkitty/locale/en_AU creating build/lib/hyperkitty/locale/en_AU/LC_MESSAGES copying hyperkitty/locale/en_AU/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/en_AU/LC_MESSAGES creating build/lib/hyperkitty/locale/en_CA creating build/lib/hyperkitty/locale/en_CA/LC_MESSAGES copying hyperkitty/locale/en_CA/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/en_CA/LC_MESSAGES creating build/lib/hyperkitty/locale/en_GB creating build/lib/hyperkitty/locale/en_GB/LC_MESSAGES copying hyperkitty/locale/en_GB/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/en_GB/LC_MESSAGES creating build/lib/hyperkitty/locale/eo creating build/lib/hyperkitty/locale/eo/LC_MESSAGES copying hyperkitty/locale/eo/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/eo/LC_MESSAGES creating build/lib/hyperkitty/locale/es creating build/lib/hyperkitty/locale/es/LC_MESSAGES copying hyperkitty/locale/es/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/es/LC_MESSAGES creating build/lib/hyperkitty/locale/et creating build/lib/hyperkitty/locale/et/LC_MESSAGES copying hyperkitty/locale/et/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/et/LC_MESSAGES creating build/lib/hyperkitty/locale/eu creating build/lib/hyperkitty/locale/eu/LC_MESSAGES copying hyperkitty/locale/eu/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/eu/LC_MESSAGES creating build/lib/hyperkitty/locale/fa creating build/lib/hyperkitty/locale/fa/LC_MESSAGES copying hyperkitty/locale/fa/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/fa/LC_MESSAGES creating build/lib/hyperkitty/locale/fi creating build/lib/hyperkitty/locale/fi/LC_MESSAGES copying hyperkitty/locale/fi/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/fi/LC_MESSAGES creating build/lib/hyperkitty/locale/fil creating build/lib/hyperkitty/locale/fil/LC_MESSAGES copying hyperkitty/locale/fil/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/fil/LC_MESSAGES creating build/lib/hyperkitty/locale/fo creating build/lib/hyperkitty/locale/fo/LC_MESSAGES copying hyperkitty/locale/fo/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/fo/LC_MESSAGES creating build/lib/hyperkitty/locale/fr creating build/lib/hyperkitty/locale/fr/LC_MESSAGES copying hyperkitty/locale/fr/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/fr/LC_MESSAGES creating build/lib/hyperkitty/locale/fr_CA creating build/lib/hyperkitty/locale/fr_CA/LC_MESSAGES copying hyperkitty/locale/fr_CA/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/fr_CA/LC_MESSAGES creating build/lib/hyperkitty/locale/frp creating build/lib/hyperkitty/locale/frp/LC_MESSAGES copying hyperkitty/locale/frp/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/frp/LC_MESSAGES creating build/lib/hyperkitty/locale/fy creating build/lib/hyperkitty/locale/fy/LC_MESSAGES copying hyperkitty/locale/fy/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/fy/LC_MESSAGES creating build/lib/hyperkitty/locale/ga creating build/lib/hyperkitty/locale/ga/LC_MESSAGES copying hyperkitty/locale/ga/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ga/LC_MESSAGES creating build/lib/hyperkitty/locale/gd creating build/lib/hyperkitty/locale/gd/LC_MESSAGES copying hyperkitty/locale/gd/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/gd/LC_MESSAGES creating build/lib/hyperkitty/locale/gl creating build/lib/hyperkitty/locale/gl/LC_MESSAGES copying hyperkitty/locale/gl/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/gl/LC_MESSAGES creating build/lib/hyperkitty/locale/gu creating build/lib/hyperkitty/locale/gu/LC_MESSAGES copying hyperkitty/locale/gu/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/gu/LC_MESSAGES creating build/lib/hyperkitty/locale/he creating build/lib/hyperkitty/locale/he/LC_MESSAGES copying hyperkitty/locale/he/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/he/LC_MESSAGES creating build/lib/hyperkitty/locale/hi creating build/lib/hyperkitty/locale/hi/LC_MESSAGES copying hyperkitty/locale/hi/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/hi/LC_MESSAGES creating build/lib/hyperkitty/locale/hr creating build/lib/hyperkitty/locale/hr/LC_MESSAGES copying hyperkitty/locale/hr/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/hr/LC_MESSAGES creating build/lib/hyperkitty/locale/ht creating build/lib/hyperkitty/locale/ht/LC_MESSAGES copying hyperkitty/locale/ht/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ht/LC_MESSAGES creating build/lib/hyperkitty/locale/hu creating build/lib/hyperkitty/locale/hu/LC_MESSAGES copying hyperkitty/locale/hu/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/hu/LC_MESSAGES creating build/lib/hyperkitty/locale/hy creating build/lib/hyperkitty/locale/hy/LC_MESSAGES copying hyperkitty/locale/hy/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/hy/LC_MESSAGES creating build/lib/hyperkitty/locale/ia creating build/lib/hyperkitty/locale/ia/LC_MESSAGES copying hyperkitty/locale/ia/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ia/LC_MESSAGES creating build/lib/hyperkitty/locale/id creating build/lib/hyperkitty/locale/id/LC_MESSAGES copying hyperkitty/locale/id/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/id/LC_MESSAGES creating build/lib/hyperkitty/locale/is creating build/lib/hyperkitty/locale/is/LC_MESSAGES copying hyperkitty/locale/is/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/is/LC_MESSAGES creating build/lib/hyperkitty/locale/it creating build/lib/hyperkitty/locale/it/LC_MESSAGES copying hyperkitty/locale/it/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/it/LC_MESSAGES creating build/lib/hyperkitty/locale/ja creating build/lib/hyperkitty/locale/ja/LC_MESSAGES copying hyperkitty/locale/ja/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ja/LC_MESSAGES creating build/lib/hyperkitty/locale/ka creating build/lib/hyperkitty/locale/ka/LC_MESSAGES copying hyperkitty/locale/ka/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ka/LC_MESSAGES creating build/lib/hyperkitty/locale/kk creating build/lib/hyperkitty/locale/kk/LC_MESSAGES copying hyperkitty/locale/kk/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/kk/LC_MESSAGES creating build/lib/hyperkitty/locale/kl creating build/lib/hyperkitty/locale/kl/LC_MESSAGES copying hyperkitty/locale/kl/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/kl/LC_MESSAGES creating build/lib/hyperkitty/locale/km creating build/lib/hyperkitty/locale/km/LC_MESSAGES copying hyperkitty/locale/km/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/km/LC_MESSAGES creating build/lib/hyperkitty/locale/kn creating build/lib/hyperkitty/locale/kn/LC_MESSAGES copying hyperkitty/locale/kn/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/kn/LC_MESSAGES creating build/lib/hyperkitty/locale/ko creating build/lib/hyperkitty/locale/ko/LC_MESSAGES copying hyperkitty/locale/ko/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ko/LC_MESSAGES creating build/lib/hyperkitty/locale/ku creating build/lib/hyperkitty/locale/ku/LC_MESSAGES copying hyperkitty/locale/ku/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ku/LC_MESSAGES creating build/lib/hyperkitty/locale/kw creating build/lib/hyperkitty/locale/kw/LC_MESSAGES copying hyperkitty/locale/kw/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/kw/LC_MESSAGES creating build/lib/hyperkitty/locale/ky creating build/lib/hyperkitty/locale/ky/LC_MESSAGES copying hyperkitty/locale/ky/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ky/LC_MESSAGES creating build/lib/hyperkitty/locale/la creating build/lib/hyperkitty/locale/la/LC_MESSAGES copying hyperkitty/locale/la/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/la/LC_MESSAGES creating build/lib/hyperkitty/locale/lb creating build/lib/hyperkitty/locale/lb/LC_MESSAGES copying hyperkitty/locale/lb/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/lb/LC_MESSAGES creating build/lib/hyperkitty/locale/lo creating build/lib/hyperkitty/locale/lo/LC_MESSAGES copying hyperkitty/locale/lo/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/lo/LC_MESSAGES creating build/lib/hyperkitty/locale/lt creating build/lib/hyperkitty/locale/lt/LC_MESSAGES copying hyperkitty/locale/lt/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/lt/LC_MESSAGES creating build/lib/hyperkitty/locale/lv creating build/lib/hyperkitty/locale/lv/LC_MESSAGES copying hyperkitty/locale/lv/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/lv/LC_MESSAGES creating build/lib/hyperkitty/locale/mg creating build/lib/hyperkitty/locale/mg/LC_MESSAGES copying hyperkitty/locale/mg/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/mg/LC_MESSAGES creating build/lib/hyperkitty/locale/mhr creating build/lib/hyperkitty/locale/mhr/LC_MESSAGES copying hyperkitty/locale/mhr/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/mhr/LC_MESSAGES creating build/lib/hyperkitty/locale/mi creating build/lib/hyperkitty/locale/mi/LC_MESSAGES copying hyperkitty/locale/mi/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/mi/LC_MESSAGES creating build/lib/hyperkitty/locale/ml creating build/lib/hyperkitty/locale/ml/LC_MESSAGES copying hyperkitty/locale/ml/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ml/LC_MESSAGES creating build/lib/hyperkitty/locale/mr creating build/lib/hyperkitty/locale/mr/LC_MESSAGES copying hyperkitty/locale/mr/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/mr/LC_MESSAGES creating build/lib/hyperkitty/locale/ms creating build/lib/hyperkitty/locale/ms/LC_MESSAGES copying hyperkitty/locale/ms/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ms/LC_MESSAGES creating build/lib/hyperkitty/locale/my creating build/lib/hyperkitty/locale/my/LC_MESSAGES copying hyperkitty/locale/my/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/my/LC_MESSAGES creating build/lib/hyperkitty/locale/nb_NO creating build/lib/hyperkitty/locale/nb_NO/LC_MESSAGES copying hyperkitty/locale/nb_NO/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/nb_NO/LC_MESSAGES creating build/lib/hyperkitty/locale/ne creating build/lib/hyperkitty/locale/ne/LC_MESSAGES copying hyperkitty/locale/ne/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ne/LC_MESSAGES creating build/lib/hyperkitty/locale/nl creating build/lib/hyperkitty/locale/nl/LC_MESSAGES copying hyperkitty/locale/nl/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/nl/LC_MESSAGES creating build/lib/hyperkitty/locale/nn_NO creating build/lib/hyperkitty/locale/nn_NO/LC_MESSAGES copying hyperkitty/locale/nn_NO/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/nn_NO/LC_MESSAGES creating build/lib/hyperkitty/locale/oc creating build/lib/hyperkitty/locale/oc/LC_MESSAGES copying hyperkitty/locale/oc/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/oc/LC_MESSAGES creating build/lib/hyperkitty/locale/os creating build/lib/hyperkitty/locale/os/LC_MESSAGES copying hyperkitty/locale/os/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/os/LC_MESSAGES creating build/lib/hyperkitty/locale/pa creating build/lib/hyperkitty/locale/pa/LC_MESSAGES copying hyperkitty/locale/pa/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/pa/LC_MESSAGES creating build/lib/hyperkitty/locale/pl creating build/lib/hyperkitty/locale/pl/LC_MESSAGES copying hyperkitty/locale/pl/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/pl/LC_MESSAGES creating build/lib/hyperkitty/locale/ps creating build/lib/hyperkitty/locale/ps/LC_MESSAGES copying hyperkitty/locale/ps/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ps/LC_MESSAGES creating build/lib/hyperkitty/locale/pt creating build/lib/hyperkitty/locale/pt/LC_MESSAGES copying hyperkitty/locale/pt/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/pt/LC_MESSAGES creating build/lib/hyperkitty/locale/pt_BR creating build/lib/hyperkitty/locale/pt_BR/LC_MESSAGES copying hyperkitty/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/pt_BR/LC_MESSAGES creating build/lib/hyperkitty/locale/ro creating build/lib/hyperkitty/locale/ro/LC_MESSAGES copying hyperkitty/locale/ro/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ro/LC_MESSAGES creating build/lib/hyperkitty/locale/ru creating build/lib/hyperkitty/locale/ru/LC_MESSAGES copying hyperkitty/locale/ru/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ru/LC_MESSAGES creating build/lib/hyperkitty/locale/sa creating build/lib/hyperkitty/locale/sa/LC_MESSAGES copying hyperkitty/locale/sa/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/sa/LC_MESSAGES creating build/lib/hyperkitty/locale/sc creating build/lib/hyperkitty/locale/sc/LC_MESSAGES copying hyperkitty/locale/sc/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/sc/LC_MESSAGES creating build/lib/hyperkitty/locale/sd creating build/lib/hyperkitty/locale/sd/LC_MESSAGES copying hyperkitty/locale/sd/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/sd/LC_MESSAGES creating build/lib/hyperkitty/locale/se creating build/lib/hyperkitty/locale/se/LC_MESSAGES copying hyperkitty/locale/se/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/se/LC_MESSAGES creating build/lib/hyperkitty/locale/shn creating build/lib/hyperkitty/locale/shn/LC_MESSAGES copying hyperkitty/locale/shn/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/shn/LC_MESSAGES creating build/lib/hyperkitty/locale/si creating build/lib/hyperkitty/locale/si/LC_MESSAGES copying hyperkitty/locale/si/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/si/LC_MESSAGES creating build/lib/hyperkitty/locale/sk creating build/lib/hyperkitty/locale/sk/LC_MESSAGES copying hyperkitty/locale/sk/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/sk/LC_MESSAGES creating build/lib/hyperkitty/locale/sl creating build/lib/hyperkitty/locale/sl/LC_MESSAGES copying hyperkitty/locale/sl/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/sl/LC_MESSAGES creating build/lib/hyperkitty/locale/sq creating build/lib/hyperkitty/locale/sq/LC_MESSAGES copying hyperkitty/locale/sq/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/sq/LC_MESSAGES creating build/lib/hyperkitty/locale/sr creating build/lib/hyperkitty/locale/sr/LC_MESSAGES copying hyperkitty/locale/sr/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/sr/LC_MESSAGES creating build/lib/hyperkitty/locale/sv creating build/lib/hyperkitty/locale/sv/LC_MESSAGES copying hyperkitty/locale/sv/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/sv/LC_MESSAGES creating build/lib/hyperkitty/locale/sw creating build/lib/hyperkitty/locale/sw/LC_MESSAGES copying hyperkitty/locale/sw/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/sw/LC_MESSAGES creating build/lib/hyperkitty/locale/szl creating build/lib/hyperkitty/locale/szl/LC_MESSAGES copying hyperkitty/locale/szl/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/szl/LC_MESSAGES creating build/lib/hyperkitty/locale/ta creating build/lib/hyperkitty/locale/ta/LC_MESSAGES copying hyperkitty/locale/ta/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ta/LC_MESSAGES creating build/lib/hyperkitty/locale/te creating build/lib/hyperkitty/locale/te/LC_MESSAGES copying hyperkitty/locale/te/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/te/LC_MESSAGES creating build/lib/hyperkitty/locale/tg creating build/lib/hyperkitty/locale/tg/LC_MESSAGES copying hyperkitty/locale/tg/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/tg/LC_MESSAGES creating build/lib/hyperkitty/locale/th creating build/lib/hyperkitty/locale/th/LC_MESSAGES copying hyperkitty/locale/th/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/th/LC_MESSAGES creating build/lib/hyperkitty/locale/ti creating build/lib/hyperkitty/locale/ti/LC_MESSAGES copying hyperkitty/locale/ti/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ti/LC_MESSAGES creating build/lib/hyperkitty/locale/tr creating build/lib/hyperkitty/locale/tr/LC_MESSAGES copying hyperkitty/locale/tr/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/tr/LC_MESSAGES creating build/lib/hyperkitty/locale/ug creating build/lib/hyperkitty/locale/ug/LC_MESSAGES copying hyperkitty/locale/ug/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ug/LC_MESSAGES creating build/lib/hyperkitty/locale/uk creating build/lib/hyperkitty/locale/uk/LC_MESSAGES copying hyperkitty/locale/uk/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/uk/LC_MESSAGES creating build/lib/hyperkitty/locale/ur creating build/lib/hyperkitty/locale/ur/LC_MESSAGES copying hyperkitty/locale/ur/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/ur/LC_MESSAGES creating build/lib/hyperkitty/locale/uz creating build/lib/hyperkitty/locale/uz/LC_MESSAGES copying hyperkitty/locale/uz/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/uz/LC_MESSAGES creating build/lib/hyperkitty/locale/vi creating build/lib/hyperkitty/locale/vi/LC_MESSAGES copying hyperkitty/locale/vi/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/vi/LC_MESSAGES creating build/lib/hyperkitty/locale/wae creating build/lib/hyperkitty/locale/wae/LC_MESSAGES copying hyperkitty/locale/wae/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/wae/LC_MESSAGES creating build/lib/hyperkitty/locale/zh_CN creating build/lib/hyperkitty/locale/zh_CN/LC_MESSAGES copying hyperkitty/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/zh_CN/LC_MESSAGES creating build/lib/hyperkitty/locale/zh_HK creating build/lib/hyperkitty/locale/zh_HK/LC_MESSAGES copying hyperkitty/locale/zh_HK/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/zh_HK/LC_MESSAGES creating build/lib/hyperkitty/locale/zh_TW creating build/lib/hyperkitty/locale/zh_TW/LC_MESSAGES copying hyperkitty/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/hyperkitty/locale/zh_TW/LC_MESSAGES creating build/lib/hyperkitty/static creating build/lib/hyperkitty/static/hyperkitty creating build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/ajax-loader.gif -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/button_back.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/button_back.svg -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/button_newer.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/button_older.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/discussion.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/email_bg.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/favicon.ico -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/hyperkitty-favicon.svg -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/hyperkitty-logo.svg -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/like.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/likealot.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/logo.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/mail-attachment.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/neutral.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/newthread.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/notsaved.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/participant.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/reply.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/saved.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/show_discussion.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/youdislike-disabled.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/youdislike.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/youlike-disabled.png -> build/lib/hyperkitty/static/hyperkitty/img copying hyperkitty/static/hyperkitty/img/youlike.png -> build/lib/hyperkitty/static/hyperkitty/img creating build/lib/hyperkitty/static/hyperkitty/js copying hyperkitty/static/hyperkitty/js/hyperkitty-common.js -> build/lib/hyperkitty/static/hyperkitty/js copying hyperkitty/static/hyperkitty/js/hyperkitty-index.js -> build/lib/hyperkitty/static/hyperkitty/js copying hyperkitty/static/hyperkitty/js/hyperkitty-overview.js -> build/lib/hyperkitty/static/hyperkitty/js copying hyperkitty/static/hyperkitty/js/hyperkitty-thread.js -> build/lib/hyperkitty/static/hyperkitty/js copying hyperkitty/static/hyperkitty/js/hyperkitty-userprofile.js -> build/lib/hyperkitty/static/hyperkitty/js creating build/lib/hyperkitty/static/hyperkitty/libs copying hyperkitty/static/hyperkitty/libs/d3.v2.min.js -> build/lib/hyperkitty/static/hyperkitty/libs copying hyperkitty/static/hyperkitty/libs/jquery.expander.js -> build/lib/hyperkitty/static/hyperkitty/libs copying hyperkitty/static/hyperkitty/libs/jquery.hotkeys.js -> build/lib/hyperkitty/static/hyperkitty/libs creating build/lib/hyperkitty/static/hyperkitty/libs/bootstrap copying hyperkitty/static/hyperkitty/libs/bootstrap/README.txt -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap creating build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/fonts creating build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap copying hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.eot -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap copying hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.svg -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap copying hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.ttf -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap copying hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.woff -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap copying hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.woff2 -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap creating build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bundle.js -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bundle.js.map -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bundle.min.js -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bundle.min.js.map -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.js -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.js.map -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.min.js -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.min.js.map -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts creating build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_alert.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_badge.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_breadcrumb.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_button-group.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_buttons.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_card.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_carousel.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_close.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_code.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_custom-forms.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_dropdown.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_forms.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_functions.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_grid.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_images.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_input-group.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_jumbotron.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_list-group.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_media.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_mixins.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_modal.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_nav.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_navbar.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_pagination.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_popover.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_print.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_progress.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_reboot.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_root.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_spinners.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_tables.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_toasts.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_tooltip.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_transitions.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_type.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_utilities.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_variables.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap-grid.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap-reboot.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets creating build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_alert.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_background-variant.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_badge.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_border-radius.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_box-shadow.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_breakpoints.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_buttons.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_caret.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_clearfix.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_deprecate.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_float.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_forms.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_gradients.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_grid-framework.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_grid.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_hover.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_image.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_list-group.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_lists.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_nav-divider.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_pagination.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_reset-text.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_resize.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_screen-reader.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_size.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_table-row.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_text-emphasis.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_text-hide.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_text-truncate.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_transition.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_visibility.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins creating build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_align.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_background.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_borders.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_clearfix.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_display.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_embed.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_flex.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_float.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_overflow.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_position.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_screenreaders.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_shadows.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_sizing.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_spacing.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_stretched-link.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_text.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_visibility.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities creating build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/vendor copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/vendor/_rfs.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/vendor creating build/lib/hyperkitty/static/hyperkitty/libs/fonts creating build/lib/hyperkitty/static/hyperkitty/libs/fonts/droid copying hyperkitty/static/hyperkitty/libs/fonts/droid/DroidSans.ttf -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/droid copying hyperkitty/static/hyperkitty/libs/fonts/droid/DroidSansMono.ttf -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/droid copying hyperkitty/static/hyperkitty/libs/fonts/droid/droid.css -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/droid creating build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome copying hyperkitty/static/hyperkitty/libs/fonts/font-awesome/VERSION.txt -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome creating build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/css copying hyperkitty/static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.css -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/css copying hyperkitty/static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.min.css -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/css creating build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts copying hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/FontAwesome.otf -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts copying hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.eot -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts copying hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.svg -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts copying hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.ttf -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts copying hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.woff -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts copying hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.woff2 -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts creating build/lib/hyperkitty/static/hyperkitty/libs/fonts/icomoon copying hyperkitty/static/hyperkitty/libs/fonts/icomoon/icomoon.css -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/icomoon creating build/lib/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts copying hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts/icomoon.eot -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts copying hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts/icomoon.svg -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts copying hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts/icomoon.ttf -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts copying hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts/icomoon.woff -> build/lib/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts creating build/lib/hyperkitty/static/hyperkitty/libs/jquery copying hyperkitty/static/hyperkitty/libs/jquery/jquery-3.6.0.js -> build/lib/hyperkitty/static/hyperkitty/libs/jquery copying hyperkitty/static/hyperkitty/libs/jquery/jquery-3.6.0.min.js -> build/lib/hyperkitty/static/hyperkitty/libs/jquery copying hyperkitty/static/hyperkitty/libs/jquery/jquery-3.6.0.min.map -> build/lib/hyperkitty/static/hyperkitty/libs/jquery copying hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.js -> build/lib/hyperkitty/static/hyperkitty/libs/jquery copying hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js -> build/lib/hyperkitty/static/hyperkitty/libs/jquery copying hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.13.1.js -> build/lib/hyperkitty/static/hyperkitty/libs/jquery copying hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.13.1.min.js -> build/lib/hyperkitty/static/hyperkitty/libs/jquery copying hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-selection.txt -> build/lib/hyperkitty/static/hyperkitty/libs/jquery creating build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.css -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.13.1.css -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.13.1.min.css -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness creating build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/animated-overlay.gif -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_flat_0_aaaaaa_40x100.png -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_flat_75_ffffff_40x100.png -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_55_fbf9ee_1x400.png -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_65_ffffff_1x400.png -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_75_dadada_1x400.png -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_75_e6e6e6_1x400.png -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_95_fef1ec_1x400.png -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_highlight-soft_75_cccccc_1x100.png -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_222222_256x240.png -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_2e83ff_256x240.png -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_454545_256x240.png -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_888888_256x240.png -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_cd0a0a_256x240.png -> build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images creating build/lib/hyperkitty/static/hyperkitty/libs/mousetrap copying hyperkitty/static/hyperkitty/libs/mousetrap/mousetrap.min.js -> build/lib/hyperkitty/static/hyperkitty/libs/mousetrap creating build/lib/hyperkitty/static/hyperkitty/libs/popper copying hyperkitty/static/hyperkitty/libs/popper/popper.js -> build/lib/hyperkitty/static/hyperkitty/libs/popper copying hyperkitty/static/hyperkitty/libs/popper/popper.js.map -> build/lib/hyperkitty/static/hyperkitty/libs/popper copying hyperkitty/static/hyperkitty/libs/popper/popper.min.js -> build/lib/hyperkitty/static/hyperkitty/libs/popper copying hyperkitty/static/hyperkitty/libs/popper/popper.min.js.map -> build/lib/hyperkitty/static/hyperkitty/libs/popper creating build/lib/hyperkitty/static/hyperkitty/sass copying hyperkitty/static/hyperkitty/sass/_hyperkitty-base.scss -> build/lib/hyperkitty/static/hyperkitty/sass copying hyperkitty/static/hyperkitty/sass/_hyperkitty-common.scss -> build/lib/hyperkitty/static/hyperkitty/sass copying hyperkitty/static/hyperkitty/sass/_hyperkitty-index.scss -> build/lib/hyperkitty/static/hyperkitty/sass copying hyperkitty/static/hyperkitty/sass/_hyperkitty-message.scss -> build/lib/hyperkitty/static/hyperkitty/sass copying hyperkitty/static/hyperkitty/sass/_hyperkitty-overview.scss -> build/lib/hyperkitty/static/hyperkitty/sass copying hyperkitty/static/hyperkitty/sass/_hyperkitty-threadslist.scss -> build/lib/hyperkitty/static/hyperkitty/sass copying hyperkitty/static/hyperkitty/sass/_hyperkitty-user.scss -> build/lib/hyperkitty/static/hyperkitty/sass copying hyperkitty/static/hyperkitty/sass/_hyperkitty-variables.scss -> build/lib/hyperkitty/static/hyperkitty/sass copying hyperkitty/static/hyperkitty/sass/hyperkitty.scss -> build/lib/hyperkitty/static/hyperkitty/sass creating build/lib/hyperkitty/static/hyperkitty/sass/bootstrap copying hyperkitty/static/hyperkitty/sass/bootstrap/_custom-grid.scss -> build/lib/hyperkitty/static/hyperkitty/sass/bootstrap copying hyperkitty/static/hyperkitty/sass/bootstrap/_custom-mixins.scss -> build/lib/hyperkitty/static/hyperkitty/sass/bootstrap copying hyperkitty/static/hyperkitty/sass/bootstrap/_custom-modals.scss -> build/lib/hyperkitty/static/hyperkitty/sass/bootstrap copying hyperkitty/static/hyperkitty/sass/bootstrap/_custom-utilities.scss -> build/lib/hyperkitty/static/hyperkitty/sass/bootstrap copying hyperkitty/static/hyperkitty/sass/bootstrap/_custom-variables.scss -> build/lib/hyperkitty/static/hyperkitty/sass/bootstrap creating build/lib/hyperkitty/templates creating build/lib/hyperkitty/templates/account copying hyperkitty/templates/account/base.html -> build/lib/hyperkitty/templates/account creating build/lib/hyperkitty/templates/django_mailman3 copying hyperkitty/templates/django_mailman3/base.html -> build/lib/hyperkitty/templates/django_mailman3 creating build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/404.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/500.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/api.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/base.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/bottom.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/headers.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/index.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/list_delete.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/message.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/message_delete.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/message_new.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/navbar-brand.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/overview.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/reattach.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/search_results.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/thread.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/thread_list.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/top.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/user_posts.html -> build/lib/hyperkitty/templates/hyperkitty copying hyperkitty/templates/hyperkitty/user_public_profile.html -> build/lib/hyperkitty/templates/hyperkitty creating build/lib/hyperkitty/templates/hyperkitty/ajax copying hyperkitty/templates/hyperkitty/ajax/reattach_suggest.html -> build/lib/hyperkitty/templates/hyperkitty/ajax copying hyperkitty/templates/hyperkitty/ajax/replies.html -> build/lib/hyperkitty/templates/hyperkitty/ajax copying hyperkitty/templates/hyperkitty/ajax/temp_message.html -> build/lib/hyperkitty/templates/hyperkitty/ajax creating build/lib/hyperkitty/templates/hyperkitty/errors copying hyperkitty/templates/hyperkitty/errors/notimplemented.html -> build/lib/hyperkitty/templates/hyperkitty/errors copying hyperkitty/templates/hyperkitty/errors/private.html -> build/lib/hyperkitty/templates/hyperkitty/errors creating build/lib/hyperkitty/templates/hyperkitty/fragments copying hyperkitty/templates/hyperkitty/fragments/like_form.html -> build/lib/hyperkitty/templates/hyperkitty/fragments copying hyperkitty/templates/hyperkitty/fragments/month_list.html -> build/lib/hyperkitty/templates/hyperkitty/fragments copying hyperkitty/templates/hyperkitty/fragments/overview_threads.html -> build/lib/hyperkitty/templates/hyperkitty/fragments copying hyperkitty/templates/hyperkitty/fragments/overview_top_posters.html -> build/lib/hyperkitty/templates/hyperkitty/fragments copying hyperkitty/templates/hyperkitty/fragments/send_as.html -> build/lib/hyperkitty/templates/hyperkitty/fragments copying hyperkitty/templates/hyperkitty/fragments/thread_left_nav.html -> build/lib/hyperkitty/templates/hyperkitty/fragments creating build/lib/hyperkitty/templates/hyperkitty/messages copying hyperkitty/templates/hyperkitty/messages/message.html -> build/lib/hyperkitty/templates/hyperkitty/messages copying hyperkitty/templates/hyperkitty/messages/right_col.html -> build/lib/hyperkitty/templates/hyperkitty/messages copying hyperkitty/templates/hyperkitty/messages/summary_message.html -> build/lib/hyperkitty/templates/hyperkitty/messages creating build/lib/hyperkitty/templates/hyperkitty/threads copying hyperkitty/templates/hyperkitty/threads/category.html -> build/lib/hyperkitty/templates/hyperkitty/threads copying hyperkitty/templates/hyperkitty/threads/right_col.html -> build/lib/hyperkitty/templates/hyperkitty/threads copying hyperkitty/templates/hyperkitty/threads/summary_thread_large.html -> build/lib/hyperkitty/templates/hyperkitty/threads copying hyperkitty/templates/hyperkitty/threads/tags.html -> build/lib/hyperkitty/templates/hyperkitty/threads creating build/lib/hyperkitty/templates/hyperkitty/user_profile copying hyperkitty/templates/hyperkitty/user_profile/base.html -> build/lib/hyperkitty/templates/hyperkitty/user_profile copying hyperkitty/templates/hyperkitty/user_profile/favorites.html -> build/lib/hyperkitty/templates/hyperkitty/user_profile copying hyperkitty/templates/hyperkitty/user_profile/last_views.html -> build/lib/hyperkitty/templates/hyperkitty/user_profile copying hyperkitty/templates/hyperkitty/user_profile/profile.html -> build/lib/hyperkitty/templates/hyperkitty/user_profile copying hyperkitty/templates/hyperkitty/user_profile/subscriptions.html -> build/lib/hyperkitty/templates/hyperkitty/user_profile copying hyperkitty/templates/hyperkitty/user_profile/votes.html -> build/lib/hyperkitty/templates/hyperkitty/user_profile creating build/lib/hyperkitty/templates/search creating build/lib/hyperkitty/templates/search/indexes creating build/lib/hyperkitty/templates/search/indexes/hyperkitty copying hyperkitty/templates/search/indexes/hyperkitty/email_subject.txt -> build/lib/hyperkitty/templates/search/indexes/hyperkitty copying hyperkitty/templates/search/indexes/hyperkitty/email_text.txt -> build/lib/hyperkitty/templates/search/indexes/hyperkitty creating build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/another-wrong-encoding.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/attachment-1.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/attachment-2.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/attachment-3.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/attachment-4.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/bad-subject-header.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/bad_content_type.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/bad_date_tz.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/bad_folding.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/cant_write_error_message.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/non-ascii-date-header.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/non-ascii-headers.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/payload-utf8-wrong.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/resent-date.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/strange-in-reply-to-header.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/unconvertable_message.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/unconvertable_msg-2.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/unicode_issue.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/unixfrom-date.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/unknown-charset.txt -> build/lib/hyperkitty/tests/testdata copying hyperkitty/tests/testdata/wrong-in-reply-to-header.txt -> build/lib/hyperkitty/tests/testdata installing to build/bdist.linux-aarch64/wheel running install running install_lib creating build/bdist.linux-aarch64 creating build/bdist.linux-aarch64/wheel creating build/bdist.linux-aarch64/wheel/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/templatetags copying build/lib/hyperkitty/templatetags/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/templatetags copying build/lib/hyperkitty/templatetags/hk_generic.py -> build/bdist.linux-aarch64/wheel/hyperkitty/templatetags copying build/lib/hyperkitty/templatetags/hk_haystack.py -> build/bdist.linux-aarch64/wheel/hyperkitty/templatetags copying build/lib/hyperkitty/templatetags/decorate.py -> build/bdist.linux-aarch64/wheel/hyperkitty/templatetags creating build/bdist.linux-aarch64/wheel/hyperkitty/static creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass copying build/lib/hyperkitty/static/hyperkitty/sass/hyperkitty.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass copying build/lib/hyperkitty/static/hyperkitty/sass/_hyperkitty-message.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass/bootstrap copying build/lib/hyperkitty/static/hyperkitty/sass/bootstrap/_custom-modals.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass/bootstrap copying build/lib/hyperkitty/static/hyperkitty/sass/bootstrap/_custom-grid.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass/bootstrap copying build/lib/hyperkitty/static/hyperkitty/sass/bootstrap/_custom-mixins.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass/bootstrap copying build/lib/hyperkitty/static/hyperkitty/sass/bootstrap/_custom-variables.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass/bootstrap copying build/lib/hyperkitty/static/hyperkitty/sass/bootstrap/_custom-utilities.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass/bootstrap copying build/lib/hyperkitty/static/hyperkitty/sass/_hyperkitty-user.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass copying build/lib/hyperkitty/static/hyperkitty/sass/_hyperkitty-index.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass copying build/lib/hyperkitty/static/hyperkitty/sass/_hyperkitty-variables.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass copying build/lib/hyperkitty/static/hyperkitty/sass/_hyperkitty-threadslist.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass copying build/lib/hyperkitty/static/hyperkitty/sass/_hyperkitty-base.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass copying build/lib/hyperkitty/static/hyperkitty/sass/_hyperkitty-overview.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass copying build/lib/hyperkitty/static/hyperkitty/sass/_hyperkitty-common.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/sass creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/mousetrap copying build/lib/hyperkitty/static/hyperkitty/libs/mousetrap/mousetrap.min.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/mousetrap copying build/lib/hyperkitty/static/hyperkitty/libs/d3.v2.min.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/font-awesome creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.ttf -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.eot -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.woff -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.woff2 -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/FontAwesome.otf -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.svg -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/css copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.css -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/css copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.min.css -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/css copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/font-awesome/VERSION.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/font-awesome creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/droid copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/droid/DroidSansMono.ttf -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/droid copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/droid/droid.css -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/droid copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/droid/DroidSans.ttf -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/droid creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/icomoon creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts/icomoon.woff -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts/icomoon.eot -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts/icomoon.svg -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts/icomoon.ttf -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts copying build/lib/hyperkitty/static/hyperkitty/libs/fonts/icomoon/icomoon.css -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/fonts/icomoon creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/popper copying build/lib/hyperkitty/static/hyperkitty/libs/popper/popper.min.js.map -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/popper copying build/lib/hyperkitty/static/hyperkitty/libs/popper/popper.min.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/popper copying build/lib/hyperkitty/static/hyperkitty/libs/popper/popper.js.map -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/popper copying build/lib/hyperkitty/static/hyperkitty/libs/popper/popper.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/popper copying build/lib/hyperkitty/static/hyperkitty/libs/jquery.hotkeys.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/fonts creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.woff2 -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.svg -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.eot -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.ttf -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.woff -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap-reboot.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_alert.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_jumbotron.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_dropdown.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_progress.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_functions.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_print.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_nav.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_mixins.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_code.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_grid.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_pagination.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_list-group.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_breadcrumb.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_modal.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_custom-forms.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_input-group.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_transitions.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_popover.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_utilities.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_buttons.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/vendor copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/vendor/_rfs.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/vendor copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_spinners.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_media.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap-grid.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_toasts.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_reboot.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_text-emphasis.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_alert.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_box-shadow.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_text-truncate.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_visibility.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_reset-text.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_grid.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_table-row.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_pagination.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_list-group.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_screen-reader.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_caret.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_resize.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_transition.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_buttons.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_size.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_text-hide.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_nav-divider.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_grid-framework.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_gradients.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_deprecate.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_clearfix.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_forms.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_image.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_border-radius.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_lists.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_hover.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_background-variant.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_badge.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_float.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_breakpoints.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_carousel.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_root.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_forms.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_navbar.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_card.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_type.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_images.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_button-group.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_close.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_spacing.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_flex.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_visibility.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_screenreaders.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_stretched-link.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_sizing.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_background.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_borders.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_position.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_display.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_text.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_align.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_clearfix.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_embed.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_shadows.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_float.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_overflow.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_tables.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_badge.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_tooltip.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_variables.scss -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bundle.min.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.min.js.map -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bundle.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bundle.min.js.map -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bundle.js.map -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.min.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.js.map -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap/javascripts copying build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/README.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/bootstrap creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.13.1.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/jquery-3.6.0.min.map -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.13.1.css -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.css -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_65_ffffff_1x400.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_flat_0_aaaaaa_40x100.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_75_dadada_1x400.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_2e83ff_256x240.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_222222_256x240.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_888888_256x240.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_454545_256x240.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/animated-overlay.gif -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_75_e6e6e6_1x400.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_95_fef1ec_1x400.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_55_fbf9ee_1x400.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_cd0a0a_256x240.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_highlight-soft_75_cccccc_1x100.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_flat_75_ffffff_40x100.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness/images copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.13.1.min.css -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery/smoothness copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/jquery-3.6.0.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/jquery-3.6.0.min.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.13.1.min.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-selection.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery copying build/lib/hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs/jquery copying build/lib/hyperkitty/static/hyperkitty/libs/jquery.expander.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/libs creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/js copying build/lib/hyperkitty/static/hyperkitty/js/hyperkitty-common.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/js copying build/lib/hyperkitty/static/hyperkitty/js/hyperkitty-index.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/js copying build/lib/hyperkitty/static/hyperkitty/js/hyperkitty-thread.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/js copying build/lib/hyperkitty/static/hyperkitty/js/hyperkitty-userprofile.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/js copying build/lib/hyperkitty/static/hyperkitty/js/hyperkitty-overview.js -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/js creating build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/youlike-disabled.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/ajax-loader.gif -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/participant.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/youdislike.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/discussion.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/like.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/button_newer.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/youlike.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/newthread.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/mail-attachment.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/button_back.svg -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/button_back.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/hyperkitty-favicon.svg -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/button_older.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/likealot.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/youdislike-disabled.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/reply.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/neutral.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/show_discussion.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/logo.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/email_bg.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/favicon.ico -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/notsaved.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/saved.png -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/static/hyperkitty/img/hyperkitty-logo.svg -> build/bdist.linux-aarch64/wheel/hyperkitty/static/hyperkitty/img copying build/lib/hyperkitty/utils.py -> build/bdist.linux-aarch64/wheel/hyperkitty copying build/lib/hyperkitty/feed.py -> build/bdist.linux-aarch64/wheel/hyperkitty copying build/lib/hyperkitty/apps.py -> build/bdist.linux-aarch64/wheel/hyperkitty copying build/lib/hyperkitty/signals.py -> build/bdist.linux-aarch64/wheel/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0002_auto_20150311_0913.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0012_thread_order_null.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0020_auto_20190907_1927.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0004_archived_date_and_subject.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0008_django_mailman3_profile.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0007_allauth_20160808_1604.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0015_mailinglist_id_3.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0023_alter_mailinglist_name.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0021_add_owners_mods.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0005_MailingList_list_id.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0006_thread_on_delete.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0022_mailinglist_archive_rendering_mode.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0016_auto_20180309_0056.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0017_file_attachments.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0010_email_sender_name.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0014_mailinglist_id_2.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0011_email_parent.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0013_mailinglist_id_1.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0018_threadcategory_color.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0003_thread_starting_email.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0009_duplicate_persona_users.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0019_auto_20190127_null_description.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/migrations/0001_initial.py -> build/bdist.linux-aarch64/wheel/hyperkitty/migrations copying build/lib/hyperkitty/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty copying build/lib/hyperkitty/forms.py -> build/bdist.linux-aarch64/wheel/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/models copying build/lib/hyperkitty/models/email.py -> build/bdist.linux-aarch64/wheel/hyperkitty/models copying build/lib/hyperkitty/models/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/models copying build/lib/hyperkitty/models/vote.py -> build/bdist.linux-aarch64/wheel/hyperkitty/models copying build/lib/hyperkitty/models/mailinglist.py -> build/bdist.linux-aarch64/wheel/hyperkitty/models copying build/lib/hyperkitty/models/category.py -> build/bdist.linux-aarch64/wheel/hyperkitty/models copying build/lib/hyperkitty/models/profile.py -> build/bdist.linux-aarch64/wheel/hyperkitty/models copying build/lib/hyperkitty/models/tag.py -> build/bdist.linux-aarch64/wheel/hyperkitty/models copying build/lib/hyperkitty/models/common.py -> build/bdist.linux-aarch64/wheel/hyperkitty/models copying build/lib/hyperkitty/models/thread.py -> build/bdist.linux-aarch64/wheel/hyperkitty/models copying build/lib/hyperkitty/models/favorite.py -> build/bdist.linux-aarch64/wheel/hyperkitty/models copying build/lib/hyperkitty/models/sender.py -> build/bdist.linux-aarch64/wheel/hyperkitty/models creating build/bdist.linux-aarch64/wheel/hyperkitty/views copying build/lib/hyperkitty/views/search.py -> build/bdist.linux-aarch64/wheel/hyperkitty/views copying build/lib/hyperkitty/views/accounts.py -> build/bdist.linux-aarch64/wheel/hyperkitty/views copying build/lib/hyperkitty/views/categories.py -> build/bdist.linux-aarch64/wheel/hyperkitty/views copying build/lib/hyperkitty/views/compat.py -> build/bdist.linux-aarch64/wheel/hyperkitty/views copying build/lib/hyperkitty/views/tags.py -> build/bdist.linux-aarch64/wheel/hyperkitty/views copying build/lib/hyperkitty/views/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/views copying build/lib/hyperkitty/views/mlist.py -> build/bdist.linux-aarch64/wheel/hyperkitty/views copying build/lib/hyperkitty/views/users.py -> build/bdist.linux-aarch64/wheel/hyperkitty/views copying build/lib/hyperkitty/views/message.py -> build/bdist.linux-aarch64/wheel/hyperkitty/views copying build/lib/hyperkitty/views/mailman.py -> build/bdist.linux-aarch64/wheel/hyperkitty/views copying build/lib/hyperkitty/views/index.py -> build/bdist.linux-aarch64/wheel/hyperkitty/views copying build/lib/hyperkitty/views/thread.py -> build/bdist.linux-aarch64/wheel/hyperkitty/views creating build/bdist.linux-aarch64/wheel/hyperkitty/locale creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/af creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/af/LC_MESSAGES copying build/lib/hyperkitty/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/af/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/hr creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/hr/LC_MESSAGES copying build/lib/hyperkitty/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/hr/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/gu creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/gu/LC_MESSAGES copying build/lib/hyperkitty/locale/gu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/gu/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/tg creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/tg/LC_MESSAGES copying build/lib/hyperkitty/locale/tg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/tg/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ast creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ast/LC_MESSAGES copying build/lib/hyperkitty/locale/ast/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ast/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/shn creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/shn/LC_MESSAGES copying build/lib/hyperkitty/locale/shn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/shn/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ky creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ky/LC_MESSAGES copying build/lib/hyperkitty/locale/ky/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ky/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/kl creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/kl/LC_MESSAGES copying build/lib/hyperkitty/locale/kl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/kl/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ru creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ru/LC_MESSAGES copying build/lib/hyperkitty/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ru/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/bs creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/bs/LC_MESSAGES copying build/lib/hyperkitty/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/bs/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/hu creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/hu/LC_MESSAGES copying build/lib/hyperkitty/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/hu/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/kw creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/kw/LC_MESSAGES copying build/lib/hyperkitty/locale/kw/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/kw/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/pl creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/pl/LC_MESSAGES copying build/lib/hyperkitty/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/pl/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/mr creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/mr/LC_MESSAGES copying build/lib/hyperkitty/locale/mr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/mr/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/zh_HK creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/zh_HK/LC_MESSAGES copying build/lib/hyperkitty/locale/zh_HK/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/zh_HK/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/gl creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/gl/LC_MESSAGES copying build/lib/hyperkitty/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/gl/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/is creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/is/LC_MESSAGES copying build/lib/hyperkitty/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/is/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/en_CA creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/en_CA/LC_MESSAGES copying build/lib/hyperkitty/locale/en_CA/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/en_CA/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/tr creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/tr/LC_MESSAGES copying build/lib/hyperkitty/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/tr/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/lv creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/lv/LC_MESSAGES copying build/lib/hyperkitty/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/lv/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ckb creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ckb/LC_MESSAGES copying build/lib/hyperkitty/locale/ckb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ckb/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sq creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sq/LC_MESSAGES copying build/lib/hyperkitty/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/sq/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fo creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fo/LC_MESSAGES copying build/lib/hyperkitty/locale/fo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/fo/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/th creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/th/LC_MESSAGES copying build/lib/hyperkitty/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/th/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/el creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/el/LC_MESSAGES copying build/lib/hyperkitty/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/el/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ar creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ar/LC_MESSAGES copying build/lib/hyperkitty/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ar/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sa creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sa/LC_MESSAGES copying build/lib/hyperkitty/locale/sa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/sa/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/hy creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/hy/LC_MESSAGES copying build/lib/hyperkitty/locale/hy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/hy/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/en_GB creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/en_GB/LC_MESSAGES copying build/lib/hyperkitty/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/en_GB/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/cy creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/cy/LC_MESSAGES copying build/lib/hyperkitty/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/cy/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ml creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ml/LC_MESSAGES copying build/lib/hyperkitty/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ml/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ca creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ca/LC_MESSAGES copying build/lib/hyperkitty/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ca/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/pt_BR creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/pt_BR/LC_MESSAGES copying build/lib/hyperkitty/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/nb_NO creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/nb_NO/LC_MESSAGES copying build/lib/hyperkitty/locale/nb_NO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/nb_NO/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ur creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ur/LC_MESSAGES copying build/lib/hyperkitty/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ur/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/kn creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/kn/LC_MESSAGES copying build/lib/hyperkitty/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/kn/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/cv creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/cv/LC_MESSAGES copying build/lib/hyperkitty/locale/cv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/cv/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/km creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/km/LC_MESSAGES copying build/lib/hyperkitty/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/km/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/nn_NO creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/nn_NO/LC_MESSAGES copying build/lib/hyperkitty/locale/nn_NO/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/nn_NO/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/an creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/an/LC_MESSAGES copying build/lib/hyperkitty/locale/an/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/an/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/wae creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/wae/LC_MESSAGES copying build/lib/hyperkitty/locale/wae/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/wae/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fy creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fy/LC_MESSAGES copying build/lib/hyperkitty/locale/fy/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/fy/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fr_CA creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fr_CA/LC_MESSAGES copying build/lib/hyperkitty/locale/fr_CA/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/fr_CA/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/oc creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/oc/LC_MESSAGES copying build/lib/hyperkitty/locale/oc/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/oc/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/et creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/et/LC_MESSAGES copying build/lib/hyperkitty/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/et/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ga creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ga/LC_MESSAGES copying build/lib/hyperkitty/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ga/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/zh_CN creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/zh_CN/LC_MESSAGES copying build/lib/hyperkitty/locale/zh_CN/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/zh_CN/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/it creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/it/LC_MESSAGES copying build/lib/hyperkitty/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/it/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ca@valencia creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ca@valencia/LC_MESSAGES copying build/lib/hyperkitty/locale/ca@valencia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ca@valencia/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/de creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/de/LC_MESSAGES copying build/lib/hyperkitty/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/de/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sk creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sk/LC_MESSAGES copying build/lib/hyperkitty/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/sk/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/co creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/co/LC_MESSAGES copying build/lib/hyperkitty/locale/co/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/co/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/cs creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/cs/LC_MESSAGES copying build/lib/hyperkitty/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/cs/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ht creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ht/LC_MESSAGES copying build/lib/hyperkitty/locale/ht/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ht/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/da creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/da/LC_MESSAGES copying build/lib/hyperkitty/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/da/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ko creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ko/LC_MESSAGES copying build/lib/hyperkitty/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ko/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/bem creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/bem/LC_MESSAGES copying build/lib/hyperkitty/locale/bem/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/bem/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/my creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/my/LC_MESSAGES copying build/lib/hyperkitty/locale/my/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/my/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/mg creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/mg/LC_MESSAGES copying build/lib/hyperkitty/locale/mg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/mg/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fa creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fa/LC_MESSAGES copying build/lib/hyperkitty/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/fa/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ka creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ka/LC_MESSAGES copying build/lib/hyperkitty/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ka/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/be creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/be/LC_MESSAGES copying build/lib/hyperkitty/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/be/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sc creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sc/LC_MESSAGES copying build/lib/hyperkitty/locale/sc/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/sc/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/zh_TW creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/zh_TW/LC_MESSAGES copying build/lib/hyperkitty/locale/zh_TW/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/zh_TW/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ti creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ti/LC_MESSAGES copying build/lib/hyperkitty/locale/ti/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ti/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/id creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/id/LC_MESSAGES copying build/lib/hyperkitty/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/id/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ms creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ms/LC_MESSAGES copying build/lib/hyperkitty/locale/ms/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ms/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/en_AU creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/en_AU/LC_MESSAGES copying build/lib/hyperkitty/locale/en_AU/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/en_AU/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/eu creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/eu/LC_MESSAGES copying build/lib/hyperkitty/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/eu/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/lo creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/lo/LC_MESSAGES copying build/lib/hyperkitty/locale/lo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/lo/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/mi creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/mi/LC_MESSAGES copying build/lib/hyperkitty/locale/mi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/mi/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/uz creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/uz/LC_MESSAGES copying build/lib/hyperkitty/locale/uz/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/uz/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ps creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ps/LC_MESSAGES copying build/lib/hyperkitty/locale/ps/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ps/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sd creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sd/LC_MESSAGES copying build/lib/hyperkitty/locale/sd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/sd/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/bo creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/bo/LC_MESSAGES copying build/lib/hyperkitty/locale/bo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/bo/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/eo creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/eo/LC_MESSAGES copying build/lib/hyperkitty/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/eo/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ce creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ce/LC_MESSAGES copying build/lib/hyperkitty/locale/ce/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ce/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/es creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/es/LC_MESSAGES copying build/lib/hyperkitty/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/es/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sl creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sl/LC_MESSAGES copying build/lib/hyperkitty/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/sl/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/nl creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/nl/LC_MESSAGES copying build/lib/hyperkitty/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/nl/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/gd creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/gd/LC_MESSAGES copying build/lib/hyperkitty/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/gd/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ro creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ro/LC_MESSAGES copying build/lib/hyperkitty/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ro/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/am creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/am/LC_MESSAGES copying build/lib/hyperkitty/locale/am/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/am/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/szl creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/szl/LC_MESSAGES copying build/lib/hyperkitty/locale/szl/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/szl/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ug creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ug/LC_MESSAGES copying build/lib/hyperkitty/locale/ug/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ug/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ne creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ne/LC_MESSAGES copying build/lib/hyperkitty/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ne/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/crh creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/crh/LC_MESSAGES copying build/lib/hyperkitty/locale/crh/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/crh/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/te creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/te/LC_MESSAGES copying build/lib/hyperkitty/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/te/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/os creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/os/LC_MESSAGES copying build/lib/hyperkitty/locale/os/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/os/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/he creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/he/LC_MESSAGES copying build/lib/hyperkitty/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/he/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/mhr creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/mhr/LC_MESSAGES copying build/lib/hyperkitty/locale/mhr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/mhr/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/se creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/se/LC_MESSAGES copying build/lib/hyperkitty/locale/se/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/se/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/la creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/la/LC_MESSAGES copying build/lib/hyperkitty/locale/la/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/la/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/br creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/br/LC_MESSAGES copying build/lib/hyperkitty/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/br/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fi creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fi/LC_MESSAGES copying build/lib/hyperkitty/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/fi/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/uk creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/uk/LC_MESSAGES copying build/lib/hyperkitty/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/uk/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/si creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/si/LC_MESSAGES copying build/lib/hyperkitty/locale/si/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/si/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/lt creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/lt/LC_MESSAGES copying build/lib/hyperkitty/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/lt/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/bn creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/bn/LC_MESSAGES copying build/lib/hyperkitty/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/bn/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/lb creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/lb/LC_MESSAGES copying build/lib/hyperkitty/locale/lb/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/lb/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/pa creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/pa/LC_MESSAGES copying build/lib/hyperkitty/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/pa/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fil creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fil/LC_MESSAGES copying build/lib/hyperkitty/locale/fil/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/fil/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fr creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/fr/LC_MESSAGES copying build/lib/hyperkitty/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/fr/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ia creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ia/LC_MESSAGES copying build/lib/hyperkitty/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ia/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ku creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ku/LC_MESSAGES copying build/lib/hyperkitty/locale/ku/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ku/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/kk creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/kk/LC_MESSAGES copying build/lib/hyperkitty/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/kk/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ta creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ta/LC_MESSAGES copying build/lib/hyperkitty/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ta/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/frp creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/frp/LC_MESSAGES copying build/lib/hyperkitty/locale/frp/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/frp/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/vi creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/vi/LC_MESSAGES copying build/lib/hyperkitty/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/vi/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/pt creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/pt/LC_MESSAGES copying build/lib/hyperkitty/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/pt/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/hi creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/hi/LC_MESSAGES copying build/lib/hyperkitty/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/hi/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/az creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/az/LC_MESSAGES copying build/lib/hyperkitty/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/az/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/bg creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/bg/LC_MESSAGES copying build/lib/hyperkitty/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/bg/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sv creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sv/LC_MESSAGES copying build/lib/hyperkitty/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/sv/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sr creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sr/LC_MESSAGES copying build/lib/hyperkitty/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/sr/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ja creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/ja/LC_MESSAGES copying build/lib/hyperkitty/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/ja/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sw creating build/bdist.linux-aarch64/wheel/hyperkitty/locale/sw/LC_MESSAGES copying build/lib/hyperkitty/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-aarch64/wheel/hyperkitty/locale/sw/LC_MESSAGES creating build/bdist.linux-aarch64/wheel/hyperkitty/api copying build/lib/hyperkitty/api/utils.py -> build/bdist.linux-aarch64/wheel/hyperkitty/api copying build/lib/hyperkitty/api/email.py -> build/bdist.linux-aarch64/wheel/hyperkitty/api copying build/lib/hyperkitty/api/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/api copying build/lib/hyperkitty/api/mailinglist.py -> build/bdist.linux-aarch64/wheel/hyperkitty/api copying build/lib/hyperkitty/api/attachment.py -> build/bdist.linux-aarch64/wheel/hyperkitty/api copying build/lib/hyperkitty/api/tag.py -> build/bdist.linux-aarch64/wheel/hyperkitty/api copying build/lib/hyperkitty/api/thread.py -> build/bdist.linux-aarch64/wheel/hyperkitty/api copying build/lib/hyperkitty/api/sender.py -> build/bdist.linux-aarch64/wheel/hyperkitty/api copying build/lib/hyperkitty/admin.py -> build/bdist.linux-aarch64/wheel/hyperkitty copying build/lib/hyperkitty/tasks.py -> build/bdist.linux-aarch64/wheel/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/tests copying build/lib/hyperkitty/tests/utils.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests creating build/bdist.linux-aarch64/wheel/hyperkitty/tests/migrations copying build/lib/hyperkitty/tests/migrations/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/migrations copying build/lib/hyperkitty/tests/migrations/test_0009.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/migrations copying build/lib/hyperkitty/tests/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests creating build/bdist.linux-aarch64/wheel/hyperkitty/tests/models copying build/lib/hyperkitty/tests/models/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/models copying build/lib/hyperkitty/tests/models/test_tag.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/models copying build/lib/hyperkitty/tests/models/test_lastview.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/models copying build/lib/hyperkitty/tests/models/test_mailinglist.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/models copying build/lib/hyperkitty/tests/models/test_email.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/models copying build/lib/hyperkitty/tests/models/test_profile.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/models copying build/lib/hyperkitty/tests/models/test_vote.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/models copying build/lib/hyperkitty/tests/models/test_sender.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/models copying build/lib/hyperkitty/tests/models/test_thread.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/models copying build/lib/hyperkitty/tests/settings_test.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests creating build/bdist.linux-aarch64/wheel/hyperkitty/tests/views copying build/lib/hyperkitty/tests/views/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/views copying build/lib/hyperkitty/tests/views/test_index.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/views copying build/lib/hyperkitty/tests/views/test_search.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/views copying build/lib/hyperkitty/tests/views/test_archives.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/views copying build/lib/hyperkitty/tests/views/test_mailinglist.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/views copying build/lib/hyperkitty/tests/views/test_mailman.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/views copying build/lib/hyperkitty/tests/views/test_message.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/views copying build/lib/hyperkitty/tests/views/test_compat.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/views copying build/lib/hyperkitty/tests/views/test_accounts.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/views copying build/lib/hyperkitty/tests/views/test_thread.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/views copying build/lib/hyperkitty/tests/test_feeds.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests creating build/bdist.linux-aarch64/wheel/hyperkitty/tests/commands copying build/lib/hyperkitty/tests/commands/test_attachments_to_file.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/commands copying build/lib/hyperkitty/tests/commands/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/commands copying build/lib/hyperkitty/tests/commands/test_import.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/commands copying build/lib/hyperkitty/tests/commands/test_mailman_sync.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/commands copying build/lib/hyperkitty/tests/_test_caching.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests creating build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/cant_write_error_message.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/unconvertable_msg-2.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/non-ascii-date-header.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/resent-date.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/another-wrong-encoding.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/unixfrom-date.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/unicode_issue.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/bad_folding.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/bad_date_tz.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/attachment-4.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/attachment-2.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/bad-subject-header.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/unknown-charset.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/bad_content_type.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/attachment-3.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/strange-in-reply-to-header.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/payload-utf8-wrong.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/unconvertable_message.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/wrong-in-reply-to-header.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/non-ascii-headers.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/testdata/attachment-1.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/testdata copying build/lib/hyperkitty/tests/test_search_index.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests copying build/lib/hyperkitty/tests/test_templatetags.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests creating build/bdist.linux-aarch64/wheel/hyperkitty/tests/jobs copying build/lib/hyperkitty/tests/jobs/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/jobs copying build/lib/hyperkitty/tests/test_signals.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests copying build/lib/hyperkitty/tests/test_tasks.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests copying build/lib/hyperkitty/tests/urls_test.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests creating build/bdist.linux-aarch64/wheel/hyperkitty/tests/lib copying build/lib/hyperkitty/tests/lib/test_analysis.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/lib copying build/lib/hyperkitty/tests/lib/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/lib copying build/lib/hyperkitty/tests/lib/test_incoming.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/lib copying build/lib/hyperkitty/tests/lib/test_view_helpers.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/lib copying build/lib/hyperkitty/tests/lib/test_mailman.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/lib copying build/lib/hyperkitty/tests/lib/test_utils.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/lib copying build/lib/hyperkitty/tests/lib/test_posting.py -> build/bdist.linux-aarch64/wheel/hyperkitty/tests/lib copying build/lib/hyperkitty/search_indexes.py -> build/bdist.linux-aarch64/wheel/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/fixtures copying build/lib/hyperkitty/fixtures/first_start.json -> build/bdist.linux-aarch64/wheel/hyperkitty/fixtures copying build/lib/hyperkitty/fixtures/tag_testdata.json -> build/bdist.linux-aarch64/wheel/hyperkitty/fixtures creating build/bdist.linux-aarch64/wheel/hyperkitty/jobs copying build/lib/hyperkitty/jobs/update_and_clean_index.py -> build/bdist.linux-aarch64/wheel/hyperkitty/jobs copying build/lib/hyperkitty/jobs/empty_threads.py -> build/bdist.linux-aarch64/wheel/hyperkitty/jobs copying build/lib/hyperkitty/jobs/recent_threads_cache.py -> build/bdist.linux-aarch64/wheel/hyperkitty/jobs copying build/lib/hyperkitty/jobs/orphan_emails.py -> build/bdist.linux-aarch64/wheel/hyperkitty/jobs copying build/lib/hyperkitty/jobs/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/jobs copying build/lib/hyperkitty/jobs/thread_starting_email.py -> build/bdist.linux-aarch64/wheel/hyperkitty/jobs copying build/lib/hyperkitty/jobs/update_index.py -> build/bdist.linux-aarch64/wheel/hyperkitty/jobs copying build/lib/hyperkitty/jobs/new_lists_from_mailman.py -> build/bdist.linux-aarch64/wheel/hyperkitty/jobs copying build/lib/hyperkitty/jobs/thread_order_depth.py -> build/bdist.linux-aarch64/wheel/hyperkitty/jobs copying build/lib/hyperkitty/jobs/sync_mailman.py -> build/bdist.linux-aarch64/wheel/hyperkitty/jobs copying build/lib/hyperkitty/urls.py -> build/bdist.linux-aarch64/wheel/hyperkitty copying build/lib/hyperkitty/context_processors.py -> build/bdist.linux-aarch64/wheel/hyperkitty copying build/lib/hyperkitty/checks.py -> build/bdist.linux-aarch64/wheel/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/templates creating build/bdist.linux-aarch64/wheel/hyperkitty/templates/search creating build/bdist.linux-aarch64/wheel/hyperkitty/templates/search/indexes creating build/bdist.linux-aarch64/wheel/hyperkitty/templates/search/indexes/hyperkitty copying build/lib/hyperkitty/templates/search/indexes/hyperkitty/email_text.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/search/indexes/hyperkitty copying build/lib/hyperkitty/templates/search/indexes/hyperkitty/email_subject.txt -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/search/indexes/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/templates/account copying build/lib/hyperkitty/templates/account/base.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/account creating build/bdist.linux-aarch64/wheel/hyperkitty/templates/django_mailman3 copying build/lib/hyperkitty/templates/django_mailman3/base.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/django_mailman3 creating build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/reattach.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/thread.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/messages copying build/lib/hyperkitty/templates/hyperkitty/messages/summary_message.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/messages copying build/lib/hyperkitty/templates/hyperkitty/messages/message.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/messages copying build/lib/hyperkitty/templates/hyperkitty/messages/right_col.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/messages copying build/lib/hyperkitty/templates/hyperkitty/500.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/message_new.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/errors copying build/lib/hyperkitty/templates/hyperkitty/errors/private.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/errors copying build/lib/hyperkitty/templates/hyperkitty/errors/notimplemented.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/errors copying build/lib/hyperkitty/templates/hyperkitty/top.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/user_posts.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/ajax copying build/lib/hyperkitty/templates/hyperkitty/ajax/reattach_suggest.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/ajax copying build/lib/hyperkitty/templates/hyperkitty/ajax/replies.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/ajax copying build/lib/hyperkitty/templates/hyperkitty/ajax/temp_message.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/ajax copying build/lib/hyperkitty/templates/hyperkitty/404.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/base.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/navbar-brand.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/message_delete.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/list_delete.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/search_results.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/bottom.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/api.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/index.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/headers.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/fragments copying build/lib/hyperkitty/templates/hyperkitty/fragments/overview_threads.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/fragments copying build/lib/hyperkitty/templates/hyperkitty/fragments/thread_left_nav.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/fragments copying build/lib/hyperkitty/templates/hyperkitty/fragments/overview_top_posters.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/fragments copying build/lib/hyperkitty/templates/hyperkitty/fragments/send_as.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/fragments copying build/lib/hyperkitty/templates/hyperkitty/fragments/like_form.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/fragments copying build/lib/hyperkitty/templates/hyperkitty/fragments/month_list.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/fragments copying build/lib/hyperkitty/templates/hyperkitty/message.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/thread_list.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/threads copying build/lib/hyperkitty/templates/hyperkitty/threads/tags.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/threads copying build/lib/hyperkitty/templates/hyperkitty/threads/summary_thread_large.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/threads copying build/lib/hyperkitty/templates/hyperkitty/threads/category.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/threads copying build/lib/hyperkitty/templates/hyperkitty/threads/right_col.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/threads creating build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/user_profile copying build/lib/hyperkitty/templates/hyperkitty/user_profile/favorites.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/user_profile copying build/lib/hyperkitty/templates/hyperkitty/user_profile/profile.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/user_profile copying build/lib/hyperkitty/templates/hyperkitty/user_profile/last_views.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/user_profile copying build/lib/hyperkitty/templates/hyperkitty/user_profile/subscriptions.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/user_profile copying build/lib/hyperkitty/templates/hyperkitty/user_profile/base.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/user_profile copying build/lib/hyperkitty/templates/hyperkitty/user_profile/votes.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty/user_profile copying build/lib/hyperkitty/templates/hyperkitty/overview.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty copying build/lib/hyperkitty/templates/hyperkitty/user_public_profile.html -> build/bdist.linux-aarch64/wheel/hyperkitty/templates/hyperkitty creating build/bdist.linux-aarch64/wheel/hyperkitty/management copying build/lib/hyperkitty/management/utils.py -> build/bdist.linux-aarch64/wheel/hyperkitty/management copying build/lib/hyperkitty/management/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/management creating build/bdist.linux-aarch64/wheel/hyperkitty/management/commands copying build/lib/hyperkitty/management/commands/hyperkitty_warm_up_cache.py -> build/bdist.linux-aarch64/wheel/hyperkitty/management/commands copying build/lib/hyperkitty/management/commands/attachments_to_file.py -> build/bdist.linux-aarch64/wheel/hyperkitty/management/commands copying build/lib/hyperkitty/management/commands/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/management/commands copying build/lib/hyperkitty/management/commands/update_index_one_list.py -> build/bdist.linux-aarch64/wheel/hyperkitty/management/commands copying build/lib/hyperkitty/management/commands/mailman_sync.py -> build/bdist.linux-aarch64/wheel/hyperkitty/management/commands copying build/lib/hyperkitty/management/commands/hyperkitty_import.py -> build/bdist.linux-aarch64/wheel/hyperkitty/management/commands creating build/bdist.linux-aarch64/wheel/hyperkitty/lib copying build/lib/hyperkitty/lib/view_helpers.py -> build/bdist.linux-aarch64/wheel/hyperkitty/lib copying build/lib/hyperkitty/lib/utils.py -> build/bdist.linux-aarch64/wheel/hyperkitty/lib copying build/lib/hyperkitty/lib/mockup.py -> build/bdist.linux-aarch64/wheel/hyperkitty/lib copying build/lib/hyperkitty/lib/analysis.py -> build/bdist.linux-aarch64/wheel/hyperkitty/lib copying build/lib/hyperkitty/lib/compat.py -> build/bdist.linux-aarch64/wheel/hyperkitty/lib copying build/lib/hyperkitty/lib/__init__.py -> build/bdist.linux-aarch64/wheel/hyperkitty/lib copying build/lib/hyperkitty/lib/incoming.py -> build/bdist.linux-aarch64/wheel/hyperkitty/lib copying build/lib/hyperkitty/lib/user.py -> build/bdist.linux-aarch64/wheel/hyperkitty/lib copying build/lib/hyperkitty/lib/posting.py -> build/bdist.linux-aarch64/wheel/hyperkitty/lib copying build/lib/hyperkitty/lib/mailman.py -> build/bdist.linux-aarch64/wheel/hyperkitty/lib copying build/lib/hyperkitty/lib/renderer.py -> build/bdist.linux-aarch64/wheel/hyperkitty/lib running install_egg_info Copying HyperKitty.egg-info to build/bdist.linux-aarch64/wheel/HyperKitty-1.3.7-py3.11.egg-info running install_scripts creating build/bdist.linux-aarch64/wheel/HyperKitty-1.3.7.dist-info/WHEEL creating '/builddir/build/BUILD/HyperKitty-1.3.7/.pyproject-builddir/pip-wheel-pzrv2j18/.tmp-lk1zh_jw/HyperKitty-1.3.7-py3-none-any.whl' and adding 'build/bdist.linux-aarch64/wheel' to it adding 'hyperkitty/__init__.py' adding 'hyperkitty/admin.py' adding 'hyperkitty/apps.py' adding 'hyperkitty/checks.py' adding 'hyperkitty/context_processors.py' adding 'hyperkitty/feed.py' adding 'hyperkitty/forms.py' adding 'hyperkitty/search_indexes.py' adding 'hyperkitty/signals.py' adding 'hyperkitty/tasks.py' adding 'hyperkitty/urls.py' adding 'hyperkitty/utils.py' adding 'hyperkitty/api/__init__.py' adding 'hyperkitty/api/attachment.py' adding 'hyperkitty/api/email.py' adding 'hyperkitty/api/mailinglist.py' adding 'hyperkitty/api/sender.py' adding 'hyperkitty/api/tag.py' adding 'hyperkitty/api/thread.py' adding 'hyperkitty/api/utils.py' adding 'hyperkitty/fixtures/first_start.json' adding 'hyperkitty/fixtures/tag_testdata.json' adding 'hyperkitty/jobs/__init__.py' adding 'hyperkitty/jobs/empty_threads.py' adding 'hyperkitty/jobs/new_lists_from_mailman.py' adding 'hyperkitty/jobs/orphan_emails.py' adding 'hyperkitty/jobs/recent_threads_cache.py' adding 'hyperkitty/jobs/sync_mailman.py' adding 'hyperkitty/jobs/thread_order_depth.py' adding 'hyperkitty/jobs/thread_starting_email.py' adding 'hyperkitty/jobs/update_and_clean_index.py' adding 'hyperkitty/jobs/update_index.py' adding 'hyperkitty/lib/__init__.py' adding 'hyperkitty/lib/analysis.py' adding 'hyperkitty/lib/compat.py' adding 'hyperkitty/lib/incoming.py' adding 'hyperkitty/lib/mailman.py' adding 'hyperkitty/lib/mockup.py' adding 'hyperkitty/lib/posting.py' adding 'hyperkitty/lib/renderer.py' adding 'hyperkitty/lib/user.py' adding 'hyperkitty/lib/utils.py' adding 'hyperkitty/lib/view_helpers.py' adding 'hyperkitty/locale/af/LC_MESSAGES/django.po' adding 'hyperkitty/locale/am/LC_MESSAGES/django.po' adding 'hyperkitty/locale/an/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ar/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ast/LC_MESSAGES/django.po' adding 'hyperkitty/locale/az/LC_MESSAGES/django.po' adding 'hyperkitty/locale/be/LC_MESSAGES/django.po' adding 'hyperkitty/locale/bem/LC_MESSAGES/django.po' adding 'hyperkitty/locale/bg/LC_MESSAGES/django.po' adding 'hyperkitty/locale/bn/LC_MESSAGES/django.po' adding 'hyperkitty/locale/bo/LC_MESSAGES/django.po' adding 'hyperkitty/locale/br/LC_MESSAGES/django.po' adding 'hyperkitty/locale/bs/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ca/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ca@valencia/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ce/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ckb/LC_MESSAGES/django.po' adding 'hyperkitty/locale/co/LC_MESSAGES/django.po' adding 'hyperkitty/locale/crh/LC_MESSAGES/django.po' adding 'hyperkitty/locale/cs/LC_MESSAGES/django.po' adding 'hyperkitty/locale/cv/LC_MESSAGES/django.po' adding 'hyperkitty/locale/cy/LC_MESSAGES/django.po' adding 'hyperkitty/locale/da/LC_MESSAGES/django.po' adding 'hyperkitty/locale/de/LC_MESSAGES/django.po' adding 'hyperkitty/locale/el/LC_MESSAGES/django.po' adding 'hyperkitty/locale/en_AU/LC_MESSAGES/django.po' adding 'hyperkitty/locale/en_CA/LC_MESSAGES/django.po' adding 'hyperkitty/locale/en_GB/LC_MESSAGES/django.po' adding 'hyperkitty/locale/eo/LC_MESSAGES/django.po' adding 'hyperkitty/locale/es/LC_MESSAGES/django.po' adding 'hyperkitty/locale/et/LC_MESSAGES/django.po' adding 'hyperkitty/locale/eu/LC_MESSAGES/django.po' adding 'hyperkitty/locale/fa/LC_MESSAGES/django.po' adding 'hyperkitty/locale/fi/LC_MESSAGES/django.po' adding 'hyperkitty/locale/fil/LC_MESSAGES/django.po' adding 'hyperkitty/locale/fo/LC_MESSAGES/django.po' adding 'hyperkitty/locale/fr/LC_MESSAGES/django.po' adding 'hyperkitty/locale/fr_CA/LC_MESSAGES/django.po' adding 'hyperkitty/locale/frp/LC_MESSAGES/django.po' adding 'hyperkitty/locale/fy/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ga/LC_MESSAGES/django.po' adding 'hyperkitty/locale/gd/LC_MESSAGES/django.po' adding 'hyperkitty/locale/gl/LC_MESSAGES/django.po' adding 'hyperkitty/locale/gu/LC_MESSAGES/django.po' adding 'hyperkitty/locale/he/LC_MESSAGES/django.po' adding 'hyperkitty/locale/hi/LC_MESSAGES/django.po' adding 'hyperkitty/locale/hr/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ht/LC_MESSAGES/django.po' adding 'hyperkitty/locale/hu/LC_MESSAGES/django.po' adding 'hyperkitty/locale/hy/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ia/LC_MESSAGES/django.po' adding 'hyperkitty/locale/id/LC_MESSAGES/django.po' adding 'hyperkitty/locale/is/LC_MESSAGES/django.po' adding 'hyperkitty/locale/it/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ja/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ka/LC_MESSAGES/django.po' adding 'hyperkitty/locale/kk/LC_MESSAGES/django.po' adding 'hyperkitty/locale/kl/LC_MESSAGES/django.po' adding 'hyperkitty/locale/km/LC_MESSAGES/django.po' adding 'hyperkitty/locale/kn/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ko/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ku/LC_MESSAGES/django.po' adding 'hyperkitty/locale/kw/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ky/LC_MESSAGES/django.po' adding 'hyperkitty/locale/la/LC_MESSAGES/django.po' adding 'hyperkitty/locale/lb/LC_MESSAGES/django.po' adding 'hyperkitty/locale/lo/LC_MESSAGES/django.po' adding 'hyperkitty/locale/lt/LC_MESSAGES/django.po' adding 'hyperkitty/locale/lv/LC_MESSAGES/django.po' adding 'hyperkitty/locale/mg/LC_MESSAGES/django.po' adding 'hyperkitty/locale/mhr/LC_MESSAGES/django.po' adding 'hyperkitty/locale/mi/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ml/LC_MESSAGES/django.po' adding 'hyperkitty/locale/mr/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ms/LC_MESSAGES/django.po' adding 'hyperkitty/locale/my/LC_MESSAGES/django.po' adding 'hyperkitty/locale/nb_NO/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ne/LC_MESSAGES/django.po' adding 'hyperkitty/locale/nl/LC_MESSAGES/django.po' adding 'hyperkitty/locale/nn_NO/LC_MESSAGES/django.po' adding 'hyperkitty/locale/oc/LC_MESSAGES/django.po' adding 'hyperkitty/locale/os/LC_MESSAGES/django.po' adding 'hyperkitty/locale/pa/LC_MESSAGES/django.po' adding 'hyperkitty/locale/pl/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ps/LC_MESSAGES/django.po' adding 'hyperkitty/locale/pt/LC_MESSAGES/django.po' adding 'hyperkitty/locale/pt_BR/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ro/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ru/LC_MESSAGES/django.po' adding 'hyperkitty/locale/sa/LC_MESSAGES/django.po' adding 'hyperkitty/locale/sc/LC_MESSAGES/django.po' adding 'hyperkitty/locale/sd/LC_MESSAGES/django.po' adding 'hyperkitty/locale/se/LC_MESSAGES/django.po' adding 'hyperkitty/locale/shn/LC_MESSAGES/django.po' adding 'hyperkitty/locale/si/LC_MESSAGES/django.po' adding 'hyperkitty/locale/sk/LC_MESSAGES/django.po' adding 'hyperkitty/locale/sl/LC_MESSAGES/django.po' adding 'hyperkitty/locale/sq/LC_MESSAGES/django.po' adding 'hyperkitty/locale/sr/LC_MESSAGES/django.po' adding 'hyperkitty/locale/sv/LC_MESSAGES/django.po' adding 'hyperkitty/locale/sw/LC_MESSAGES/django.po' adding 'hyperkitty/locale/szl/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ta/LC_MESSAGES/django.po' adding 'hyperkitty/locale/te/LC_MESSAGES/django.po' adding 'hyperkitty/locale/tg/LC_MESSAGES/django.po' adding 'hyperkitty/locale/th/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ti/LC_MESSAGES/django.po' adding 'hyperkitty/locale/tr/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ug/LC_MESSAGES/django.po' adding 'hyperkitty/locale/uk/LC_MESSAGES/django.po' adding 'hyperkitty/locale/ur/LC_MESSAGES/django.po' adding 'hyperkitty/locale/uz/LC_MESSAGES/django.po' adding 'hyperkitty/locale/vi/LC_MESSAGES/django.po' adding 'hyperkitty/locale/wae/LC_MESSAGES/django.po' adding 'hyperkitty/locale/zh_CN/LC_MESSAGES/django.po' adding 'hyperkitty/locale/zh_HK/LC_MESSAGES/django.po' adding 'hyperkitty/locale/zh_TW/LC_MESSAGES/django.po' adding 'hyperkitty/management/__init__.py' adding 'hyperkitty/management/utils.py' adding 'hyperkitty/management/commands/__init__.py' adding 'hyperkitty/management/commands/attachments_to_file.py' adding 'hyperkitty/management/commands/hyperkitty_import.py' adding 'hyperkitty/management/commands/hyperkitty_warm_up_cache.py' adding 'hyperkitty/management/commands/mailman_sync.py' adding 'hyperkitty/management/commands/update_index_one_list.py' adding 'hyperkitty/migrations/0001_initial.py' adding 'hyperkitty/migrations/0002_auto_20150311_0913.py' adding 'hyperkitty/migrations/0003_thread_starting_email.py' adding 'hyperkitty/migrations/0004_archived_date_and_subject.py' adding 'hyperkitty/migrations/0005_MailingList_list_id.py' adding 'hyperkitty/migrations/0006_thread_on_delete.py' adding 'hyperkitty/migrations/0007_allauth_20160808_1604.py' adding 'hyperkitty/migrations/0008_django_mailman3_profile.py' adding 'hyperkitty/migrations/0009_duplicate_persona_users.py' adding 'hyperkitty/migrations/0010_email_sender_name.py' adding 'hyperkitty/migrations/0011_email_parent.py' adding 'hyperkitty/migrations/0012_thread_order_null.py' adding 'hyperkitty/migrations/0013_mailinglist_id_1.py' adding 'hyperkitty/migrations/0014_mailinglist_id_2.py' adding 'hyperkitty/migrations/0015_mailinglist_id_3.py' adding 'hyperkitty/migrations/0016_auto_20180309_0056.py' adding 'hyperkitty/migrations/0017_file_attachments.py' adding 'hyperkitty/migrations/0018_threadcategory_color.py' adding 'hyperkitty/migrations/0019_auto_20190127_null_description.py' adding 'hyperkitty/migrations/0020_auto_20190907_1927.py' adding 'hyperkitty/migrations/0021_add_owners_mods.py' adding 'hyperkitty/migrations/0022_mailinglist_archive_rendering_mode.py' adding 'hyperkitty/migrations/0023_alter_mailinglist_name.py' adding 'hyperkitty/migrations/__init__.py' adding 'hyperkitty/models/__init__.py' adding 'hyperkitty/models/category.py' adding 'hyperkitty/models/common.py' adding 'hyperkitty/models/email.py' adding 'hyperkitty/models/favorite.py' adding 'hyperkitty/models/mailinglist.py' adding 'hyperkitty/models/profile.py' adding 'hyperkitty/models/sender.py' adding 'hyperkitty/models/tag.py' adding 'hyperkitty/models/thread.py' adding 'hyperkitty/models/vote.py' adding 'hyperkitty/static/hyperkitty/img/ajax-loader.gif' adding 'hyperkitty/static/hyperkitty/img/button_back.png' adding 'hyperkitty/static/hyperkitty/img/button_back.svg' adding 'hyperkitty/static/hyperkitty/img/button_newer.png' adding 'hyperkitty/static/hyperkitty/img/button_older.png' adding 'hyperkitty/static/hyperkitty/img/discussion.png' adding 'hyperkitty/static/hyperkitty/img/email_bg.png' adding 'hyperkitty/static/hyperkitty/img/favicon.ico' adding 'hyperkitty/static/hyperkitty/img/hyperkitty-favicon.svg' adding 'hyperkitty/static/hyperkitty/img/hyperkitty-logo.svg' adding 'hyperkitty/static/hyperkitty/img/like.png' adding 'hyperkitty/static/hyperkitty/img/likealot.png' adding 'hyperkitty/static/hyperkitty/img/logo.png' adding 'hyperkitty/static/hyperkitty/img/mail-attachment.png' adding 'hyperkitty/static/hyperkitty/img/neutral.png' adding 'hyperkitty/static/hyperkitty/img/newthread.png' adding 'hyperkitty/static/hyperkitty/img/notsaved.png' adding 'hyperkitty/static/hyperkitty/img/participant.png' adding 'hyperkitty/static/hyperkitty/img/reply.png' adding 'hyperkitty/static/hyperkitty/img/saved.png' adding 'hyperkitty/static/hyperkitty/img/show_discussion.png' adding 'hyperkitty/static/hyperkitty/img/youdislike-disabled.png' adding 'hyperkitty/static/hyperkitty/img/youdislike.png' adding 'hyperkitty/static/hyperkitty/img/youlike-disabled.png' adding 'hyperkitty/static/hyperkitty/img/youlike.png' adding 'hyperkitty/static/hyperkitty/js/hyperkitty-common.js' adding 'hyperkitty/static/hyperkitty/js/hyperkitty-index.js' adding 'hyperkitty/static/hyperkitty/js/hyperkitty-overview.js' adding 'hyperkitty/static/hyperkitty/js/hyperkitty-thread.js' adding 'hyperkitty/static/hyperkitty/js/hyperkitty-userprofile.js' adding 'hyperkitty/static/hyperkitty/libs/d3.v2.min.js' adding 'hyperkitty/static/hyperkitty/libs/jquery.expander.js' adding 'hyperkitty/static/hyperkitty/libs/jquery.hotkeys.js' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/README.txt' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.eot' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.svg' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.ttf' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.woff' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/fonts/bootstrap/glyphicons-halflings-regular.woff2' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bundle.js' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bundle.js.map' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bundle.min.js' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.bundle.min.js.map' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.js' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.js.map' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.min.js' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/javascripts/bootstrap.min.js.map' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_alert.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_badge.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_breadcrumb.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_button-group.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_buttons.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_card.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_carousel.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_close.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_code.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_custom-forms.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_dropdown.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_forms.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_functions.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_grid.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_images.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_input-group.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_jumbotron.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_list-group.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_media.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_mixins.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_modal.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_nav.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_navbar.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_pagination.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_popover.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_print.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_progress.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_reboot.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_root.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_spinners.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_tables.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_toasts.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_tooltip.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_transitions.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_type.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_utilities.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_variables.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap-grid.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap-reboot.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/bootstrap.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_alert.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_background-variant.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_badge.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_border-radius.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_box-shadow.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_breakpoints.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_buttons.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_caret.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_clearfix.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_deprecate.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_float.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_forms.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_gradients.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_grid-framework.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_grid.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_hover.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_image.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_list-group.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_lists.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_nav-divider.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_pagination.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_reset-text.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_resize.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_screen-reader.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_size.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_table-row.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_text-emphasis.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_text-hide.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_text-truncate.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_transition.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_visibility.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_align.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_background.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_borders.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_clearfix.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_display.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_embed.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_flex.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_float.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_overflow.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_position.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_screenreaders.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_shadows.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_sizing.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_spacing.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_stretched-link.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_text.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/utilities/_visibility.scss' adding 'hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/vendor/_rfs.scss' adding 'hyperkitty/static/hyperkitty/libs/fonts/droid/DroidSans.ttf' adding 'hyperkitty/static/hyperkitty/libs/fonts/droid/DroidSansMono.ttf' adding 'hyperkitty/static/hyperkitty/libs/fonts/droid/droid.css' adding 'hyperkitty/static/hyperkitty/libs/fonts/font-awesome/VERSION.txt' adding 'hyperkitty/static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.css' adding 'hyperkitty/static/hyperkitty/libs/fonts/font-awesome/css/font-awesome.min.css' adding 'hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/FontAwesome.otf' adding 'hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.eot' adding 'hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.svg' adding 'hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.ttf' adding 'hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.woff' adding 'hyperkitty/static/hyperkitty/libs/fonts/font-awesome/fonts/fontawesome-webfont.woff2' adding 'hyperkitty/static/hyperkitty/libs/fonts/icomoon/icomoon.css' adding 'hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts/icomoon.eot' adding 'hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts/icomoon.svg' adding 'hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts/icomoon.ttf' adding 'hyperkitty/static/hyperkitty/libs/fonts/icomoon/fonts/icomoon.woff' adding 'hyperkitty/static/hyperkitty/libs/jquery/jquery-3.6.0.js' adding 'hyperkitty/static/hyperkitty/libs/jquery/jquery-3.6.0.min.js' adding 'hyperkitty/static/hyperkitty/libs/jquery/jquery-3.6.0.min.map' adding 'hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.js' adding 'hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.10.3.custom.min.js' adding 'hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.13.1.js' adding 'hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-1.13.1.min.js' adding 'hyperkitty/static/hyperkitty/libs/jquery/jquery-ui-selection.txt' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.css' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.10.3.custom.min.css' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.13.1.css' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/jquery-ui-1.13.1.min.css' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/animated-overlay.gif' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_flat_0_aaaaaa_40x100.png' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_flat_75_ffffff_40x100.png' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_55_fbf9ee_1x400.png' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_65_ffffff_1x400.png' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_75_dadada_1x400.png' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_75_e6e6e6_1x400.png' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_glass_95_fef1ec_1x400.png' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-bg_highlight-soft_75_cccccc_1x100.png' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_222222_256x240.png' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_2e83ff_256x240.png' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_454545_256x240.png' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_888888_256x240.png' adding 'hyperkitty/static/hyperkitty/libs/jquery/smoothness/images/ui-icons_cd0a0a_256x240.png' adding 'hyperkitty/static/hyperkitty/libs/mousetrap/mousetrap.min.js' adding 'hyperkitty/static/hyperkitty/libs/popper/popper.js' adding 'hyperkitty/static/hyperkitty/libs/popper/popper.js.map' adding 'hyperkitty/static/hyperkitty/libs/popper/popper.min.js' adding 'hyperkitty/static/hyperkitty/libs/popper/popper.min.js.map' adding 'hyperkitty/static/hyperkitty/sass/_hyperkitty-base.scss' adding 'hyperkitty/static/hyperkitty/sass/_hyperkitty-common.scss' adding 'hyperkitty/static/hyperkitty/sass/_hyperkitty-index.scss' adding 'hyperkitty/static/hyperkitty/sass/_hyperkitty-message.scss' adding 'hyperkitty/static/hyperkitty/sass/_hyperkitty-overview.scss' adding 'hyperkitty/static/hyperkitty/sass/_hyperkitty-threadslist.scss' adding 'hyperkitty/static/hyperkitty/sass/_hyperkitty-user.scss' adding 'hyperkitty/static/hyperkitty/sass/_hyperkitty-variables.scss' adding 'hyperkitty/static/hyperkitty/sass/hyperkitty.scss' adding 'hyperkitty/static/hyperkitty/sass/bootstrap/_custom-grid.scss' adding 'hyperkitty/static/hyperkitty/sass/bootstrap/_custom-mixins.scss' adding 'hyperkitty/static/hyperkitty/sass/bootstrap/_custom-modals.scss' adding 'hyperkitty/static/hyperkitty/sass/bootstrap/_custom-utilities.scss' adding 'hyperkitty/static/hyperkitty/sass/bootstrap/_custom-variables.scss' adding 'hyperkitty/templates/account/base.html' adding 'hyperkitty/templates/django_mailman3/base.html' adding 'hyperkitty/templates/hyperkitty/404.html' adding 'hyperkitty/templates/hyperkitty/500.html' adding 'hyperkitty/templates/hyperkitty/api.html' adding 'hyperkitty/templates/hyperkitty/base.html' adding 'hyperkitty/templates/hyperkitty/bottom.html' adding 'hyperkitty/templates/hyperkitty/headers.html' adding 'hyperkitty/templates/hyperkitty/index.html' adding 'hyperkitty/templates/hyperkitty/list_delete.html' adding 'hyperkitty/templates/hyperkitty/message.html' adding 'hyperkitty/templates/hyperkitty/message_delete.html' adding 'hyperkitty/templates/hyperkitty/message_new.html' adding 'hyperkitty/templates/hyperkitty/navbar-brand.html' adding 'hyperkitty/templates/hyperkitty/overview.html' adding 'hyperkitty/templates/hyperkitty/reattach.html' adding 'hyperkitty/templates/hyperkitty/search_results.html' adding 'hyperkitty/templates/hyperkitty/thread.html' adding 'hyperkitty/templates/hyperkitty/thread_list.html' adding 'hyperkitty/templates/hyperkitty/top.html' adding 'hyperkitty/templates/hyperkitty/user_posts.html' adding 'hyperkitty/templates/hyperkitty/user_public_profile.html' adding 'hyperkitty/templates/hyperkitty/ajax/reattach_suggest.html' adding 'hyperkitty/templates/hyperkitty/ajax/replies.html' adding 'hyperkitty/templates/hyperkitty/ajax/temp_message.html' adding 'hyperkitty/templates/hyperkitty/errors/notimplemented.html' adding 'hyperkitty/templates/hyperkitty/errors/private.html' adding 'hyperkitty/templates/hyperkitty/fragments/like_form.html' adding 'hyperkitty/templates/hyperkitty/fragments/month_list.html' adding 'hyperkitty/templates/hyperkitty/fragments/overview_threads.html' adding 'hyperkitty/templates/hyperkitty/fragments/overview_top_posters.html' adding 'hyperkitty/templates/hyperkitty/fragments/send_as.html' adding 'hyperkitty/templates/hyperkitty/fragments/thread_left_nav.html' adding 'hyperkitty/templates/hyperkitty/messages/message.html' adding 'hyperkitty/templates/hyperkitty/messages/right_col.html' adding 'hyperkitty/templates/hyperkitty/messages/summary_message.html' adding 'hyperkitty/templates/hyperkitty/threads/category.html' adding 'hyperkitty/templates/hyperkitty/threads/right_col.html' adding 'hyperkitty/templates/hyperkitty/threads/summary_thread_large.html' adding 'hyperkitty/templates/hyperkitty/threads/tags.html' adding 'hyperkitty/templates/hyperkitty/user_profile/base.html' adding 'hyperkitty/templates/hyperkitty/user_profile/favorites.html' adding 'hyperkitty/templates/hyperkitty/user_profile/last_views.html' adding 'hyperkitty/templates/hyperkitty/user_profile/profile.html' adding 'hyperkitty/templates/hyperkitty/user_profile/subscriptions.html' adding 'hyperkitty/templates/hyperkitty/user_profile/votes.html' adding 'hyperkitty/templates/search/indexes/hyperkitty/email_subject.txt' adding 'hyperkitty/templates/search/indexes/hyperkitty/email_text.txt' adding 'hyperkitty/templatetags/__init__.py' adding 'hyperkitty/templatetags/decorate.py' adding 'hyperkitty/templatetags/hk_generic.py' adding 'hyperkitty/templatetags/hk_haystack.py' adding 'hyperkitty/tests/__init__.py' adding 'hyperkitty/tests/_test_caching.py' adding 'hyperkitty/tests/settings_test.py' adding 'hyperkitty/tests/test_feeds.py' adding 'hyperkitty/tests/test_search_index.py' adding 'hyperkitty/tests/test_signals.py' adding 'hyperkitty/tests/test_tasks.py' adding 'hyperkitty/tests/test_templatetags.py' adding 'hyperkitty/tests/urls_test.py' adding 'hyperkitty/tests/utils.py' adding 'hyperkitty/tests/commands/__init__.py' adding 'hyperkitty/tests/commands/test_attachments_to_file.py' adding 'hyperkitty/tests/commands/test_import.py' adding 'hyperkitty/tests/commands/test_mailman_sync.py' adding 'hyperkitty/tests/jobs/__init__.py' adding 'hyperkitty/tests/lib/__init__.py' adding 'hyperkitty/tests/lib/test_analysis.py' adding 'hyperkitty/tests/lib/test_incoming.py' adding 'hyperkitty/tests/lib/test_mailman.py' adding 'hyperkitty/tests/lib/test_posting.py' adding 'hyperkitty/tests/lib/test_utils.py' adding 'hyperkitty/tests/lib/test_view_helpers.py' adding 'hyperkitty/tests/migrations/__init__.py' adding 'hyperkitty/tests/migrations/test_0009.py' adding 'hyperkitty/tests/models/__init__.py' adding 'hyperkitty/tests/models/test_email.py' adding 'hyperkitty/tests/models/test_lastview.py' adding 'hyperkitty/tests/models/test_mailinglist.py' adding 'hyperkitty/tests/models/test_profile.py' adding 'hyperkitty/tests/models/test_sender.py' adding 'hyperkitty/tests/models/test_tag.py' adding 'hyperkitty/tests/models/test_thread.py' adding 'hyperkitty/tests/models/test_vote.py' adding 'hyperkitty/tests/testdata/another-wrong-encoding.txt' adding 'hyperkitty/tests/testdata/attachment-1.txt' adding 'hyperkitty/tests/testdata/attachment-2.txt' adding 'hyperkitty/tests/testdata/attachment-3.txt' adding 'hyperkitty/tests/testdata/attachment-4.txt' adding 'hyperkitty/tests/testdata/bad-subject-header.txt' adding 'hyperkitty/tests/testdata/bad_content_type.txt' adding 'hyperkitty/tests/testdata/bad_date_tz.txt' adding 'hyperkitty/tests/testdata/bad_folding.txt' adding 'hyperkitty/tests/testdata/cant_write_error_message.txt' adding 'hyperkitty/tests/testdata/non-ascii-date-header.txt' adding 'hyperkitty/tests/testdata/non-ascii-headers.txt' adding 'hyperkitty/tests/testdata/payload-utf8-wrong.txt' adding 'hyperkitty/tests/testdata/resent-date.txt' adding 'hyperkitty/tests/testdata/strange-in-reply-to-header.txt' adding 'hyperkitty/tests/testdata/unconvertable_message.txt' adding 'hyperkitty/tests/testdata/unconvertable_msg-2.txt' adding 'hyperkitty/tests/testdata/unicode_issue.txt' adding 'hyperkitty/tests/testdata/unixfrom-date.txt' adding 'hyperkitty/tests/testdata/unknown-charset.txt' adding 'hyperkitty/tests/testdata/wrong-in-reply-to-header.txt' adding 'hyperkitty/tests/views/__init__.py' adding 'hyperkitty/tests/views/test_accounts.py' adding 'hyperkitty/tests/views/test_archives.py' adding 'hyperkitty/tests/views/test_compat.py' adding 'hyperkitty/tests/views/test_index.py' adding 'hyperkitty/tests/views/test_mailinglist.py' adding 'hyperkitty/tests/views/test_mailman.py' adding 'hyperkitty/tests/views/test_message.py' adding 'hyperkitty/tests/views/test_search.py' adding 'hyperkitty/tests/views/test_thread.py' adding 'hyperkitty/views/__init__.py' adding 'hyperkitty/views/accounts.py' adding 'hyperkitty/views/categories.py' adding 'hyperkitty/views/compat.py' adding 'hyperkitty/views/index.py' adding 'hyperkitty/views/mailman.py' adding 'hyperkitty/views/message.py' adding 'hyperkitty/views/mlist.py' adding 'hyperkitty/views/search.py' adding 'hyperkitty/views/tags.py' adding 'hyperkitty/views/thread.py' adding 'hyperkitty/views/users.py' adding 'HyperKitty-1.3.7.dist-info/AUTHORS.txt' adding 'HyperKitty-1.3.7.dist-info/COPYING.txt' adding 'HyperKitty-1.3.7.dist-info/METADATA' adding 'HyperKitty-1.3.7.dist-info/WHEEL' adding 'HyperKitty-1.3.7.dist-info/top_level.txt' adding 'HyperKitty-1.3.7.dist-info/RECORD' removing build/bdist.linux-aarch64/wheel Building wheel for HyperKitty (pyproject.toml): finished with status 'done' Created wheel for HyperKitty: filename=HyperKitty-1.3.7-py3-none-any.whl size=2945550 sha256=aec7cdb5a1146dc8fc9a9530e87cdb5049cfe1b29189628b6b2feca5b0fa5c4d Stored in directory: /builddir/.cache/pip/wheels/4f/95/8f/642e6a88cd67c54e593f45fb1095bf8031d7cc7c670e84b9ee Successfully built HyperKitty + cd doc + PYTHONPATH=..: + make html sphinx-build -b html -d _build/doctrees . _build/html Running Sphinx v7.0.1 making output directory... done WARNING: html_static_path entry '_static' does not exist building [mo]: targets for 0 po files that are out of date writing output... building [html]: targets for 5 source files that are out of date updating environment: [new config] 5 added, 0 changed, 0 removed reading sources... [ 20%] development reading sources... [ 40%] index reading sources... [ 60%] install reading sources... [ 80%] news reading sources... [100%] rendering looking for now-outdated files... none found pickling environment... done checking consistency... done preparing documents... done writing output... [ 20%] development writing output... [ 40%] index writing output... [ 60%] install writing output... [ 80%] news writing output... [100%] rendering generating indices... genindex done writing additional pages... search done copying static files... done copying extra files... done dumping search index in English (code: en)... done dumping object inventory... done build succeeded, 1 warning. The HTML pages are in _build/html. Build finished. The HTML pages are in _build/html. + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.WQbWd4 + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch '!=' / ']' + rm -rf /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch ++ dirname /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch + cd HyperKitty-1.3.7 ++ ls /builddir/build/BUILD/HyperKitty-1.3.7/pyproject-wheeldir/HyperKitty-1.3.7-py3-none-any.whl ++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/' ++ xargs basename --multiple + specifier=HyperKitty==1.3.7 + TMPDIR=/builddir/build/BUILD/HyperKitty-1.3.7/.pyproject-builddir + /usr/bin/python3 -m pip install --root /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch --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/HyperKitty-1.3.7/pyproject-wheeldir HyperKitty==1.3.7 Using pip 23.3.1 from /usr/lib/python3.11/site-packages/pip (python 3.11) Looking in links: /builddir/build/BUILD/HyperKitty-1.3.7/pyproject-wheeldir Processing ./pyproject-wheeldir/HyperKitty-1.3.7-py3-none-any.whl Installing collected packages: HyperKitty Successfully installed HyperKitty-1.3.7 + '[' -d /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/bin ']' + rm -f /builddir/build/BUILD/pyproject-ghost-distinfo + site_dirs=() + '[' -d /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/lib/python3.11/site-packages ']' + site_dirs+=("/usr/lib/python3.11/site-packages") + '[' /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/lib64/python3.11/site-packages '!=' /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/lib/python3.11/site-packages ']' + '[' -d /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/lib64/python3.11/site-packages ']' + for site_dir in ${site_dirs[@]} + for distinfo in /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch$site_dir/*.dist-info + echo '%ghost /usr/lib/python3.11/site-packages/HyperKitty-1.3.7.dist-info' + sed -i s/pip/rpm/ /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/lib/python3.11/site-packages/HyperKitty-1.3.7.dist-info/INSTALLER + PYTHONPATH=/usr/lib/rpm/OpenCloudOS + /usr/bin/python3 -B /usr/lib/rpm/OpenCloudOS/pyproject_preprocess_record.py --buildroot /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch --record /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/lib/python3.11/site-packages/HyperKitty-1.3.7.dist-info/RECORD --output /builddir/build/BUILD/pyproject-record + rm -fv /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/lib/python3.11/site-packages/HyperKitty-1.3.7.dist-info/RECORD removed '/builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/lib/python3.11/site-packages/HyperKitty-1.3.7.dist-info/RECORD' + rm -fv /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/lib/python3.11/site-packages/HyperKitty-1.3.7.dist-info/REQUESTED removed '/builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/lib/python3.11/site-packages/HyperKitty-1.3.7.dist-info/REQUESTED' + /usr/bin/python3 /usr/lib/rpm/OpenCloudOS/pyproject_save_files.py --output-files /builddir/build/BUILD/pyproject-files --output-modules /builddir/build/BUILD/pyproject-modules --buildroot /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch --sitelib /usr/lib/python3.11/site-packages --sitearch /usr/lib64/python3.11/site-packages --python-version 3.11 --pyproject-record /builddir/build/BUILD/pyproject-record --prefix /usr hyperkitty + /usr/bin/find-debuginfo -j8 --strict-build-id -m -i --build-id-seed 1.3.7-1.oc9 --unique-debug-suffix -1.3.7-1.oc9.noarch --unique-debug-src-base python-hyperkitty-1.3.7-1.oc9.noarch -S debugsourcefiles.list /builddir/build/BUILD/HyperKitty-1.3.7 find: 'debug': No such file or directory + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/OpenCloudOS/brp-ldconfig + /usr/lib/rpm/brp-compress + /usr/lib/rpm/OpenCloudOS/brp-strip-lto /usr/bin/strip + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/OpenCloudOS/brp-mangle-shebangs + /usr/lib/rpm/OpenCloudOS/brp-python-bytecompile '' 1 0 Bytecompiling .py files below /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/lib/python3.11 using python3.11 + /usr/lib/rpm/OpenCloudOS/brp-python-hardlink Processing files: hyperkitty-1.3.7-1.oc9.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.d6N9g7 + umask 022 + cd /builddir/build/BUILD + cd HyperKitty-1.3.7 + DOCDIR=/builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/share/doc/hyperkitty + export LC_ALL=C + LC_ALL=C + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/share/doc/hyperkitty + cp -pr AUTHORS.txt /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/share/doc/hyperkitty + cp -pr README.rst /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/share/doc/hyperkitty + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.f8eTXT + umask 022 + cd /builddir/build/BUILD + cd HyperKitty-1.3.7 + LICENSEDIR=/builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/share/licenses/hyperkitty + export LC_ALL=C + LC_ALL=C + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/share/licenses/hyperkitty + cp -pr COPYING.txt /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/share/licenses/hyperkitty + RPM_EC=0 ++ jobs -p + exit 0 Provides: hyperkitty = 1.3.7-1.oc9 python3.11dist(hyperkitty) = 1.3.7 python3dist(hyperkitty) = 1.3.7 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: (python3.11dist(django) < 4.3~~ with python3.11dist(django) >= 3.2) (python3.11dist(mistune) < 3~~ with python3.11dist(mistune) >= 2) python(abi) = 3.11 python3.11dist(django-compressor) >= 1.3 python3.11dist(django-extensions) >= 1.3.7 python3.11dist(django-gravatar2) >= 1.0.6 python3.11dist(django-haystack) >= 2.8 python3.11dist(django-mailman3) >= 1.3.8 python3.11dist(django-q) >= 1 python3.11dist(djangorestframework) >= 3 python3.11dist(flufl-lock) >= 4 python3.11dist(mailmanclient) >= 3.3.3 python3.11dist(networkx) >= 2 python3.11dist(python-dateutil) >= 2 python3.11dist(pytz) >= 2012 python3.11dist(robot-detection) >= 0.3 Processing files: hyperkitty-doc-1.3.7-1.oc9.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.UCQVmN + umask 022 + cd /builddir/build/BUILD + cd HyperKitty-1.3.7 + DOCDIR=/builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/share/doc/hyperkitty-doc + export LC_ALL=C + LC_ALL=C + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/share/doc/hyperkitty-doc + cp -pr doc/_build/html/_sources doc/_build/html/_static doc/_build/html/development.html doc/_build/html/genindex.html doc/_build/html/index.html doc/_build/html/install.html doc/_build/html/news.html doc/_build/html/objects.inv doc/_build/html/rendering.html doc/_build/html/search.html doc/_build/html/searchindex.js /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/share/doc/hyperkitty-doc + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.StPHBy + umask 022 + cd /builddir/build/BUILD + cd HyperKitty-1.3.7 + LICENSEDIR=/builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/share/licenses/hyperkitty-doc + export LC_ALL=C + LC_ALL=C + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/share/licenses/hyperkitty-doc + cp -pr COPYING.txt /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch/usr/share/licenses/hyperkitty-doc + RPM_EC=0 ++ jobs -p + exit 0 Provides: hyperkitty-doc = 1.3.7-1.oc9 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Suggests: hyperkitty = 1.3.7-1.oc9 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/python-hyperkitty-1.3.7-1.oc9.noarch Wrote: /builddir/build/SRPMS/python-hyperkitty-1.3.7-1.oc9.src.rpm Wrote: /builddir/build/RPMS/hyperkitty-doc-1.3.7-1.oc9.noarch.rpm Wrote: /builddir/build/RPMS/hyperkitty-1.3.7-1.oc9.noarch.rpm Child return code was: 0