=> Bootstrap dependency digest>=20211023: found digest-20220214 ===> Skipping vulnerability checks. WARNING: No /usr/pkg/pkgdb/pkg-vulnerabilities file found. WARNING: To fix run: `/usr/sbin/pkg_admin -K /usr/pkg/pkgdb fetch-pkg-vulnerabilities'. ===> Building for py312-hyperkitty-1.3.8 (cd /tmp/www/py-hyperkitty/work/HyperKitty-1.3.8/ && /usr/bin/env USETOOLS=no PTHREAD_CFLAGS=\ -pthread\ PTHREAD_LDFLAGS=\ -pthread PTHREAD_LIBS= PTHREADBASE=/usr DL_CFLAGS=\ -pthread\ DL_LDFLAGS=\ -pthread DL_LIBS= PYTHON=/usr/pkg/bin/python3.12 CC=gcc CFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.12 CPPFLAGS=-I/usr/include\ -I/usr/pkg/include/python3.12 CXX=c++ CXXFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.12 COMPILER_RPATH_FLAG=-Wl,-R F77=gfortran FC=gfortran FFLAGS=-O LANG=C LC_ALL=C LC_COLLATE=C LC_CTYPE=C LC_MESSAGES=C LC_MONETARY=C LC_NUMERIC=C LC_TIME=C LDFLAGS=-Wl,-zrelro\ -L/usr/lib\ -Wl,-R/usr/lib\ -Wl,-R/usr/pkg/lib LINKER_RPATH_FLAG=-R PATH=/tmp/www/py-hyperkitty/work/.cwrapper/bin:/tmp/www/py-hyperkitty/work/.buildlink/bin:/tmp/www/py-hyperkitty/work/.tools/bin:/usr/pkg/bin:/usr/bin:/bin:/usr/pkg/bin:/usr/local/bin:/usr/pkg/bin:/usr/X11R7/bin PREFIX=/usr/pkg MAKELEVEL=0 CONFIG_SITE= PKG_SYSCONFDIR=/usr/pkg/etc CPP=cpp CXXCPP=cpp HOME=/tmp/www/py-hyperkitty/work/.home CWRAPPERS_CONFIG_DIR=/tmp/www/py-hyperkitty/work/.cwrapper/config CPP=cpp LOCALBASE=/usr/pkg X11BASE=/usr/X11R7 PKGMANDIR=man PKGINFODIR=info PKGGNUDIR=gnu/ MAKECONF=/dev/null OBJECT_FMT=ELF USETOOLS=no BSD_INSTALL_PROGRAM=/usr/bin/install\ -c\ -s\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_SCRIPT=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_LIB=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_DATA=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 644 BSD_INSTALL_MAN=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 644 BSD_INSTALL=/usr/bin/install BSD_INSTALL_PROGRAM_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_SCRIPT_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_LIB_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_DATA_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_MAN_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 755 BSD_INSTALL_GAME=/usr/bin/install\ -c\ -s\ -o\ pbulk\ -g\ wheel\ -m\ 2555 BSD_INSTALL_GAME_DATA=/usr/bin/install\ -c\ -o\ pbulk\ -g\ wheel\ -m\ 664 BSD_INSTALL_GAME_DIR=/usr/bin/install\ -d\ -o\ pbulk\ -g\ wheel\ -m\ 775 INSTALL_INFO= MAKEINFO=/tmp/www/py-hyperkitty/work/.tools/bin/makeinfo FLEX= BISON= ITSTOOL=/tmp/www/py-hyperkitty/work/.tools/bin/itstool GDBUS_CODEGEN=/tmp/www/py-hyperkitty/work/.tools/bin/gdbus-codegen PKG_CONFIG=/tmp/www/py-hyperkitty/work/.tools/bin/pkg-config PKG_CONFIG_LIBDIR=/tmp/www/py-hyperkitty/work/.buildlink/lib/pkgconfig:/tmp/www/py-hyperkitty/work/.buildlink/share/pkgconfig PKG_CONFIG_LOG=/tmp/www/py-hyperkitty/work/.pkg-config.log PKG_CONFIG_PATH= CWRAPPERS_CONFIG_DIR=/tmp/www/py-hyperkitty/work/.cwrapper/config /usr/pkg/bin/python3.12 setup.py build -j4) /tmp/www/py-hyperkitty/work/HyperKitty-1.3.8/setup.py:29: SyntaxWarning: invalid escape sequence '\s' mo = re.match("""VERSION\s*=\s*['"](?P[^'"]+?)['"]""", line) /usr/pkg/lib/python3.12/site-packages/setuptools/__init__.py:80: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! ******************************************************************************** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. ******************************************************************************** !! dist.fetch_build_eggs(dist.setup_requires) WARNING: The wheel package is not available. running build running build_py creating build creating build/lib creating build/lib/hyperkitty copying hyperkitty/__init__.py -> build/lib/hyperkitty copying hyperkitty/admin.py -> build/lib/hyperkitty copying hyperkitty/apps.py -> build/lib/hyperkitty copying hyperkitty/checks.py -> build/lib/hyperkitty copying hyperkitty/context_processors.py -> build/lib/hyperkitty copying hyperkitty/feed.py -> build/lib/hyperkitty copying hyperkitty/forms.py -> build/lib/hyperkitty copying hyperkitty/search_indexes.py -> build/lib/hyperkitty copying hyperkitty/signals.py -> build/lib/hyperkitty copying hyperkitty/tasks.py -> build/lib/hyperkitty copying hyperkitty/urls.py -> build/lib/hyperkitty copying hyperkitty/utils.py -> build/lib/hyperkitty creating build/lib/hyperkitty/api copying hyperkitty/api/__init__.py -> build/lib/hyperkitty/api copying hyperkitty/api/attachment.py -> build/lib/hyperkitty/api copying hyperkitty/api/email.py -> build/lib/hyperkitty/api copying hyperkitty/api/mailinglist.py -> build/lib/hyperkitty/api copying hyperkitty/api/sender.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/utils.py -> build/lib/hyperkitty/api creating build/lib/hyperkitty/jobs copying hyperkitty/jobs/__init__.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/empty_threads.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/new_lists_from_mailman.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/orphan_emails.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/recent_threads_cache.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/sync_mailman.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/thread_order_depth.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/thread_starting_email.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/update_and_clean_index.py -> build/lib/hyperkitty/jobs copying hyperkitty/jobs/update_index.py -> build/lib/hyperkitty/jobs creating build/lib/hyperkitty/lib copying hyperkitty/lib/__init__.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/incoming.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/mailman.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/mockup.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/posting.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/renderer.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/user.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/utils.py -> build/lib/hyperkitty/lib copying hyperkitty/lib/view_helpers.py -> build/lib/hyperkitty/lib creating build/lib/hyperkitty/management copying hyperkitty/management/__init__.py -> build/lib/hyperkitty/management copying hyperkitty/management/utils.py -> build/lib/hyperkitty/management creating build/lib/hyperkitty/migrations copying hyperkitty/migrations/0001_initial.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0002_auto_20150311_0913.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0003_thread_starting_email.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0004_archived_date_and_subject.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/0007_allauth_20160808_1604.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0008_django_mailman3_profile.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0009_duplicate_persona_users.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0010_email_sender_name.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0011_email_parent.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0012_thread_order_null.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0013_mailinglist_id_1.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0014_mailinglist_id_2.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0015_mailinglist_id_3.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/0018_threadcategory_color.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0019_auto_20190127_null_description.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0020_auto_20190907_1927.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0021_add_owners_mods.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0022_mailinglist_archive_rendering_mode.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/0023_alter_mailinglist_name.py -> build/lib/hyperkitty/migrations copying hyperkitty/migrations/__init__.py -> build/lib/hyperkitty/migrations creating build/lib/hyperkitty/models copying hyperkitty/models/__init__.py -> build/lib/hyperkitty/models copying hyperkitty/models/category.py -> build/lib/hyperkitty/models copying hyperkitty/models/common.py -> build/lib/hyperkitty/models copying hyperkitty/models/email.py -> build/lib/hyperkitty/models copying hyperkitty/models/favorite.py -> build/lib/hyperkitty/models copying hyperkitty/models/mailinglist.py -> build/lib/hyperkitty/models copying hyperkitty/models/profile.py -> build/lib/hyperkitty/models copying hyperkitty/models/sender.py -> build/lib/hyperkitty/models copying hyperkitty/models/tag.py -> build/lib/hyperkitty/models copying hyperkitty/models/thread.py -> build/lib/hyperkitty/models copying hyperkitty/models/vote.py -> build/lib/hyperkitty/models creating build/lib/hyperkitty/templatetags copying hyperkitty/templatetags/__init__.py -> build/lib/hyperkitty/templatetags copying hyperkitty/templatetags/decorate.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 creating build/lib/hyperkitty/tests copying hyperkitty/tests/__init__.py -> build/lib/hyperkitty/tests copying hyperkitty/tests/_test_caching.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_search_index.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/test_templatetags.py -> build/lib/hyperkitty/tests copying hyperkitty/tests/urls_test.py -> build/lib/hyperkitty/tests copying hyperkitty/tests/utils.py -> build/lib/hyperkitty/tests creating build/lib/hyperkitty/views copying hyperkitty/views/__init__.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/index.py -> build/lib/hyperkitty/views copying hyperkitty/views/mailman.py -> build/lib/hyperkitty/views copying hyperkitty/views/message.py -> build/lib/hyperkitty/views copying hyperkitty/views/mlist.py -> build/lib/hyperkitty/views copying hyperkitty/views/search.py -> build/lib/hyperkitty/views copying hyperkitty/views/tags.py -> build/lib/hyperkitty/views copying hyperkitty/views/thread.py -> build/lib/hyperkitty/views copying hyperkitty/views/users.py -> build/lib/hyperkitty/views creating build/lib/hyperkitty/management/commands copying hyperkitty/management/commands/__init__.py -> build/lib/hyperkitty/management/commands copying hyperkitty/management/commands/attachments_to_file.py -> build/lib/hyperkitty/management/commands copying hyperkitty/management/commands/hyperkitty_import.py -> build/lib/hyperkitty/management/commands copying hyperkitty/management/commands/hyperkitty_warm_up_cache.py -> build/lib/hyperkitty/management/commands copying hyperkitty/management/commands/mailman_sync.py -> build/lib/hyperkitty/management/commands copying hyperkitty/management/commands/update_index_one_list.py -> build/lib/hyperkitty/management/commands creating build/lib/hyperkitty/tests/commands copying hyperkitty/tests/commands/__init__.py -> build/lib/hyperkitty/tests/commands copying hyperkitty/tests/commands/test_attachments_to_file.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/__init__.py -> build/lib/hyperkitty/tests/lib copying hyperkitty/tests/lib/test_analysis.py -> build/lib/hyperkitty/tests/lib copying hyperkitty/tests/lib/test_incoming.py -> build/lib/hyperkitty/tests/lib copying hyperkitty/tests/lib/test_mailman.py -> build/lib/hyperkitty/tests/lib copying hyperkitty/tests/lib/test_posting.py -> build/lib/hyperkitty/tests/lib copying hyperkitty/tests/lib/test_utils.py -> build/lib/hyperkitty/tests/lib copying hyperkitty/tests/lib/test_view_helpers.py -> build/lib/hyperkitty/tests/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_email.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_profile.py -> build/lib/hyperkitty/tests/models copying hyperkitty/tests/models/test_sender.py -> build/lib/hyperkitty/tests/models copying hyperkitty/tests/models/test_tag.py -> build/lib/hyperkitty/tests/models copying hyperkitty/tests/models/test_thread.py -> build/lib/hyperkitty/tests/models copying hyperkitty/tests/models/test_vote.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_accounts.py -> build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/test_archives.py -> build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/test_compat.py -> build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/test_index.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_search.py -> build/lib/hyperkitty/tests/views copying hyperkitty/tests/views/test_thread.py -> build/lib/hyperkitty/tests/views 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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.forms' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.forms' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.forms' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.forms' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.forms' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.helpers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.helpers' as an importable package[^1], but it 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.helpers' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can 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.helpers' to be distributed and are already explicitly excluding 'hyperkitty.static.hyperkitty.libs.bootstrap.stylesheets.helpers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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/pkg/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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 creating build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/_accordion.scss -> 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/_containers.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/_helpers.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/_list-group.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/_offcanvas.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/_placeholders.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/_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-utilities.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/forms copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms/_floating-labels.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms/_form-check.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms/_form-control.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms/_form-range.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms/_form-select.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms/_form-text.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms/_input-group.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms/_labels.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms/_validation.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/forms creating build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers/_clearfix.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers/_colored-links.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers/_position.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers/_ratio.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers/_stacks.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers/_stretched-link.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers/_text-truncation.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers/_visually-hidden.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers/_vr.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/helpers 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/_backdrop.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/_color-scheme.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_container.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/_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.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/_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/_table-variants.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/_utilities.scss -> build/lib/hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins copying hyperkitty/static/hyperkitty/libs/bootstrap/stylesheets/mixins/_visually-hidden.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/_api.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/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