=> 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 py39-postorius-1.3.10 (cd /tmp/www/py-postorius/work/postorius-1.3.10/ && /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.9 CC=gcc CFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.9 CPPFLAGS=-I/usr/include\ -I/usr/pkg/include/python3.9 CXX=c++ CXXFLAGS=-O2\ -I/usr/include\ -I/usr/pkg/include/python3.9 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-postorius/work/.cwrapper/bin:/tmp/www/py-postorius/work/.buildlink/bin:/tmp/www/py-postorius/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-postorius/work/.home CWRAPPERS_CONFIG_DIR=/tmp/www/py-postorius/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-postorius/work/.tools/bin/makeinfo FLEX= BISON= ITSTOOL=/tmp/www/py-postorius/work/.tools/bin/itstool GDBUS_CODEGEN=/tmp/www/py-postorius/work/.tools/bin/gdbus-codegen PKG_CONFIG=/tmp/www/py-postorius/work/.tools/bin/pkg-config PKG_CONFIG_LIBDIR=/tmp/www/py-postorius/work/.buildlink/lib/pkgconfig:/tmp/www/py-postorius/work/.buildlink/share/pkgconfig PKG_CONFIG_LOG=/tmp/www/py-postorius/work/.pkg-config.log PKG_CONFIG_PATH= CWRAPPERS_CONFIG_DIR=/tmp/www/py-postorius/work/.cwrapper/config /usr/pkg/bin/python3.9 setup.py build -j4) running build running build_py creating build creating build/lib creating build/lib/postorius copying src/postorius/__init__.py -> build/lib/postorius copying src/postorius/apps.py -> build/lib/postorius copying src/postorius/context_processors.py -> build/lib/postorius copying src/postorius/middleware.py -> build/lib/postorius copying src/postorius/models.py -> build/lib/postorius copying src/postorius/signals.py -> build/lib/postorius copying src/postorius/template_list.py -> build/lib/postorius copying src/postorius/urls.py -> build/lib/postorius copying src/postorius/utils.py -> build/lib/postorius creating build/lib/postorius/auth copying src/postorius/auth/__init__.py -> build/lib/postorius/auth copying src/postorius/auth/decorators.py -> build/lib/postorius/auth copying src/postorius/auth/mixins.py -> build/lib/postorius/auth copying src/postorius/auth/utils.py -> build/lib/postorius/auth creating build/lib/postorius/doc copying src/postorius/doc/__init__.py -> build/lib/postorius/doc copying src/postorius/doc/conf.py -> build/lib/postorius/doc copying src/postorius/doc/settings.py -> build/lib/postorius/doc creating build/lib/postorius/forms copying src/postorius/forms/__init__.py -> build/lib/postorius/forms copying src/postorius/forms/domain_forms.py -> build/lib/postorius/forms copying src/postorius/forms/fields.py -> build/lib/postorius/forms copying src/postorius/forms/list_forms.py -> build/lib/postorius/forms copying src/postorius/forms/member_forms.py -> build/lib/postorius/forms copying src/postorius/forms/system.py -> build/lib/postorius/forms copying src/postorius/forms/user_forms.py -> build/lib/postorius/forms copying src/postorius/forms/validators.py -> build/lib/postorius/forms creating build/lib/postorius/management copying src/postorius/management/__init__.py -> build/lib/postorius/management creating build/lib/postorius/migrations copying src/postorius/migrations/0001_initial.py -> build/lib/postorius/migrations copying src/postorius/migrations/0002_auto_20160210_0721.py -> build/lib/postorius/migrations copying src/postorius/migrations/0003_drop_addressconfirmationprofile.py -> build/lib/postorius/migrations copying src/postorius/migrations/0004_create_email_template.py -> build/lib/postorius/migrations copying src/postorius/migrations/0005_auto_20180707_1107.py -> build/lib/postorius/migrations copying src/postorius/migrations/0006_auto_20180711_1359.py -> build/lib/postorius/migrations copying src/postorius/migrations/0007_auto_20180712_0536.py -> build/lib/postorius/migrations copying src/postorius/migrations/0008_auto_20190310_0717.py -> build/lib/postorius/migrations copying src/postorius/migrations/0009_auto_20190508_1604.py -> build/lib/postorius/migrations copying src/postorius/migrations/0010_auto_20190821_0621.py -> build/lib/postorius/migrations copying src/postorius/migrations/0011_auto_20191109_1219.py -> build/lib/postorius/migrations copying src/postorius/migrations/0012_auto_20200420_2136.py -> build/lib/postorius/migrations copying src/postorius/migrations/0013_auto_20201116_0058.py -> build/lib/postorius/migrations copying src/postorius/migrations/0014_auto_20210329_2248.py -> build/lib/postorius/migrations copying src/postorius/migrations/0015_auto_20210619_0509.py -> build/lib/postorius/migrations copying src/postorius/migrations/0016_auto_20210810_2157.py -> build/lib/postorius/migrations copying src/postorius/migrations/0017_alter_emailtemplate_language.py -> build/lib/postorius/migrations copying src/postorius/migrations/0018_alter_emailtemplate_language.py -> build/lib/postorius/migrations copying src/postorius/migrations/__init__.py -> build/lib/postorius/migrations creating build/lib/postorius/templatetags copying src/postorius/templatetags/__init__.py -> build/lib/postorius/templatetags copying src/postorius/templatetags/date_helpers.py -> build/lib/postorius/templatetags copying src/postorius/templatetags/markdown.py -> build/lib/postorius/templatetags copying src/postorius/templatetags/membership_helpers.py -> build/lib/postorius/templatetags copying src/postorius/templatetags/nav_helpers.py -> build/lib/postorius/templatetags copying src/postorius/templatetags/p_gravatar.py -> build/lib/postorius/templatetags copying src/postorius/templatetags/postorius_helpers.py -> build/lib/postorius/templatetags creating build/lib/postorius/tests copying src/postorius/tests/__init__.py -> build/lib/postorius/tests copying src/postorius/tests/test_auth_decorators.py -> build/lib/postorius/tests copying src/postorius/tests/test_domain_forms.py -> build/lib/postorius/tests copying src/postorius/tests/test_domain_view.py -> build/lib/postorius/tests copying src/postorius/tests/test_error_pages.py -> build/lib/postorius/tests copying src/postorius/tests/test_list_forms.py -> build/lib/postorius/tests copying src/postorius/tests/test_list_view.py -> build/lib/postorius/tests copying src/postorius/tests/test_member_forms.py -> build/lib/postorius/tests copying src/postorius/tests/test_migration.py -> build/lib/postorius/tests copying src/postorius/tests/test_template_api_view.py -> build/lib/postorius/tests copying src/postorius/tests/test_templatetags.py -> build/lib/postorius/tests copying src/postorius/tests/test_urls.py -> build/lib/postorius/tests copying src/postorius/tests/test_user_forms.py -> build/lib/postorius/tests copying src/postorius/tests/test_utils.py -> build/lib/postorius/tests copying src/postorius/tests/test_validators.py -> build/lib/postorius/tests copying src/postorius/tests/utils.py -> build/lib/postorius/tests creating build/lib/postorius/views copying src/postorius/views/__init__.py -> build/lib/postorius/views copying src/postorius/views/domain.py -> build/lib/postorius/views copying src/postorius/views/generic.py -> build/lib/postorius/views copying src/postorius/views/list.py -> build/lib/postorius/views copying src/postorius/views/rest.py -> build/lib/postorius/views copying src/postorius/views/system.py -> build/lib/postorius/views copying src/postorius/views/template.py -> build/lib/postorius/views copying src/postorius/views/user.py -> build/lib/postorius/views creating build/lib/postorius/management/commands copying src/postorius/management/commands/__init__.py -> build/lib/postorius/management/commands copying src/postorius/management/commands/mmclient.py -> build/lib/postorius/management/commands copying src/postorius/management/commands/reset_passwords.py -> build/lib/postorius/management/commands creating build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/__init__.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/conftest.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_anonymous_subscribe.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_auth_utils.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_bans.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_domain_delete.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_domain_edit.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_domain_index.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_domain_new.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_generic_view.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_list_delete.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_list_header_matches.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_list_index.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_list_joinleave.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_list_member_options.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_list_members.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_list_moderation.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_list_new.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_list_settings.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_list_summary.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_membership_helpers.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_mixins.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_models.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_nav_helpers.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_rest.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_subscriptions.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_system.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_template_view.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_user.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_user_forms.py -> build/lib/postorius/tests/mailman_api_tests copying src/postorius/tests/mailman_api_tests/test_utils.py -> build/lib/postorius/tests/mailman_api_tests running egg_info writing src/postorius.egg-info/PKG-INFO writing dependency_links to src/postorius.egg-info/dependency_links.txt writing requirements to src/postorius.egg-info/requires.txt writing top-level names to src/postorius.egg-info/top_level.txt reading manifest file 'src/postorius.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'src/postorius/doc/_build' warning: no files found matching '*.txt' under directory 'example_project' warning: no previously-included files found matching 'example_project/settings_local.py' no previously-included directories found matching 'example_project/venv' no previously-included directories found matching 'example_project/static' warning: no directories found matching 'src/postorius/tests/fixtures' adding license file 'COPYING' writing manifest file 'src/postorius.egg-info/SOURCES.txt' /usr/pkg/lib/python3.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.am.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.am.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.an.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.an.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ast.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ast.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.bem.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.bem.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.bo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.bo.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ce.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ce.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ckb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ckb.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.co.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.co.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.crh.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.crh.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.cv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.cv.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.en_AU.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.en_AU.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.en_CA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.en_CA.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.fil.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.fil.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.fo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.fo.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.fr_CA.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.fr_CA.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.frp.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.frp.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.fy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.fy.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.gu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.gu.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ht.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ht.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.hy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.hy.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.kl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.kl.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ku.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ku.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.kw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.kw.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ky.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ky.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.la.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.la.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.lb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.lb.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.lo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.lo.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.mg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.mg.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.mhr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.mhr.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.mi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.mi.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.mr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.mr.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ms.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ms.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.my.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.my.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.nb_NO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.nb_NO.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.nn_NO.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.nn_NO.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.oc.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.oc.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.os.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.os.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ps.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ps.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.sa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.sa.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.sc.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.sc.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.sd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.sd.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.se.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.se.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.shn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.shn.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.si.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.si.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.szl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.szl.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.tg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.tg.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ti.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ti.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ug.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ug.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.uz.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.uz.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.wae.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.wae.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.zh_CN.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.zh_CN.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.zh_HK.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.zh_HK.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.locale.zh_TW.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.locale.zh_TW.LC_MESSAGES' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.static.postorius.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.static.postorius.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'postorius.static.postorius.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'postorius.static.postorius.css' to be distributed and are already explicitly excluding 'postorius.static.postorius.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.static.postorius.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.static.postorius.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 'postorius.static.postorius.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 'postorius.static.postorius.img' to be distributed and are already explicitly excluding 'postorius.static.postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.static.postorius.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.static.postorius.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 'postorius.static.postorius.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 'postorius.static.postorius.js' to be distributed and are already explicitly excluding 'postorius.static.postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.static.postorius.libs.bootstrap.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.static.postorius.libs.bootstrap.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'postorius.static.postorius.libs.bootstrap.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'postorius.static.postorius.libs.bootstrap.css' to be distributed and are already explicitly excluding 'postorius.static.postorius.libs.bootstrap.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.static.postorius.libs.bootstrap.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.static.postorius.libs.bootstrap.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 'postorius.static.postorius.libs.bootstrap.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 'postorius.static.postorius.libs.bootstrap.fonts' to be distributed and are already explicitly excluding 'postorius.static.postorius.libs.bootstrap.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.static.postorius.libs.bootstrap.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.static.postorius.libs.bootstrap.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 'postorius.static.postorius.libs.bootstrap.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 'postorius.static.postorius.libs.bootstrap.js' to be distributed and are already explicitly excluding 'postorius.static.postorius.libs.bootstrap.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.static.postorius.libs.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.static.postorius.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 'postorius.static.postorius.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 'postorius.static.postorius.libs.fonts' to be distributed and are already explicitly excluding 'postorius.static.postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.static.postorius.libs.jquery' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.static.postorius.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 'postorius.static.postorius.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 'postorius.static.postorius.libs.jquery' to be distributed and are already explicitly excluding 'postorius.static.postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.templates' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'postorius.templates' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'postorius.templates' to be distributed and are already explicitly excluding 'postorius.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.templates.account' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.templates.account' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.templates.django_mailman3' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.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 'postorius.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 'postorius.templates.django_mailman3' to be distributed and are already explicitly excluding 'postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.templates.postorius' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.templates.postorius' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'postorius.templates.postorius' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'postorius.templates.postorius' to be distributed and are already explicitly excluding 'postorius.templates.postorius' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.templates.postorius.domain' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.templates.postorius.domain' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'postorius.templates.postorius.domain' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'postorius.templates.postorius.domain' to be distributed and are already explicitly excluding 'postorius.templates.postorius.domain' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.templates.postorius.errors' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.templates.postorius.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 'postorius.templates.postorius.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 'postorius.templates.postorius.errors' to be distributed and are already explicitly excluding 'postorius.templates.postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.templates.postorius.fragments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.templates.postorius.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 'postorius.templates.postorius.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 'postorius.templates.postorius.fragments' to be distributed and are already explicitly excluding 'postorius.templates.postorius.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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.templates.postorius.lists' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.templates.postorius.lists' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'postorius.templates.postorius.lists' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'postorius.templates.postorius.lists' to be distributed and are already explicitly excluding 'postorius.templates.postorius.lists' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.templates.postorius.menu' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.templates.postorius.menu' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'postorius.templates.postorius.menu' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'postorius.templates.postorius.menu' to be distributed and are already explicitly excluding 'postorius.templates.postorius.menu' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.templates.postorius.user' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.templates.postorius.user' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'postorius.templates.postorius.user' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'postorius.templates.postorius.user' to be distributed and are already explicitly excluding 'postorius.templates.postorius.user' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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.9/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'postorius.tests.test_data' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'postorius.tests.test_data' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'postorius.tests.test_data' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'postorius.tests.test_data' to be distributed and are already explicitly excluding 'postorius.tests.test_data' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/postorius/locale creating build/lib/postorius/locale/af creating build/lib/postorius/locale/af/LC_MESSAGES copying src/postorius/locale/af/LC_MESSAGES/django.po -> build/lib/postorius/locale/af/LC_MESSAGES creating build/lib/postorius/locale/am creating build/lib/postorius/locale/am/LC_MESSAGES copying src/postorius/locale/am/LC_MESSAGES/django.po -> build/lib/postorius/locale/am/LC_MESSAGES creating build/lib/postorius/locale/an creating build/lib/postorius/locale/an/LC_MESSAGES copying src/postorius/locale/an/LC_MESSAGES/django.po -> build/lib/postorius/locale/an/LC_MESSAGES creating build/lib/postorius/locale/ar creating build/lib/postorius/locale/ar/LC_MESSAGES copying src/postorius/locale/ar/LC_MESSAGES/django.po -> build/lib/postorius/locale/ar/LC_MESSAGES creating build/lib/postorius/locale/ast creating build/lib/postorius/locale/ast/LC_MESSAGES copying src/postorius/locale/ast/LC_MESSAGES/django.po -> build/lib/postorius/locale/ast/LC_MESSAGES creating build/lib/postorius/locale/az creating build/lib/postorius/locale/az/LC_MESSAGES copying src/postorius/locale/az/LC_MESSAGES/django.po -> build/lib/postorius/locale/az/LC_MESSAGES creating build/lib/postorius/locale/be creating build/lib/postorius/locale/be/LC_MESSAGES copying src/postorius/locale/be/LC_MESSAGES/django.po -> build/lib/postorius/locale/be/LC_MESSAGES creating build/lib/postorius/locale/bem creating build/lib/postorius/locale/bem/LC_MESSAGES copying src/postorius/locale/bem/LC_MESSAGES/django.po -> build/lib/postorius/locale/bem/LC_MESSAGES creating build/lib/postorius/locale/bg creating build/lib/postorius/locale/bg/LC_MESSAGES copying src/postorius/locale/bg/LC_MESSAGES/django.po -> build/lib/postorius/locale/bg/LC_MESSAGES creating build/lib/postorius/locale/bn creating build/lib/postorius/locale/bn/LC_MESSAGES copying src/postorius/locale/bn/LC_MESSAGES/django.po -> build/lib/postorius/locale/bn/LC_MESSAGES creating build/lib/postorius/locale/bo creating build/lib/postorius/locale/bo/LC_MESSAGES copying src/postorius/locale/bo/LC_MESSAGES/django.po -> build/lib/postorius/locale/bo/LC_MESSAGES creating build/lib/postorius/locale/br creating build/lib/postorius/locale/br/LC_MESSAGES copying src/postorius/locale/br/LC_MESSAGES/django.po -> build/lib/postorius/locale/br/LC_MESSAGES creating build/lib/postorius/locale/bs creating build/lib/postorius/locale/bs/LC_MESSAGES copying src/postorius/locale/bs/LC_MESSAGES/django.po -> build/lib/postorius/locale/bs/LC_MESSAGES creating build/lib/postorius/locale/ca creating build/lib/postorius/locale/ca/LC_MESSAGES copying src/postorius/locale/ca/LC_MESSAGES/django.po -> build/lib/postorius/locale/ca/LC_MESSAGES creating build/lib/postorius/locale/ca@valencia creating build/lib/postorius/locale/ca@valencia/LC_MESSAGES copying src/postorius/locale/ca@valencia/LC_MESSAGES/django.po -> build/lib/postorius/locale/ca@valencia/LC_MESSAGES creating build/lib/postorius/locale/ce creating build/lib/postorius/locale/ce/LC_MESSAGES copying src/postorius/locale/ce/LC_MESSAGES/django.po -> build/lib/postorius/locale/ce/LC_MESSAGES creating build/lib/postorius/locale/ckb creating build/lib/postorius/locale/ckb/LC_MESSAGES copying src/postorius/locale/ckb/LC_MESSAGES/django.po -> build/lib/postorius/locale/ckb/LC_MESSAGES creating build/lib/postorius/locale/co creating build/lib/postorius/locale/co/LC_MESSAGES copying src/postorius/locale/co/LC_MESSAGES/django.po -> build/lib/postorius/locale/co/LC_MESSAGES creating build/lib/postorius/locale/crh creating build/lib/postorius/locale/crh/LC_MESSAGES copying src/postorius/locale/crh/LC_MESSAGES/django.po -> build/lib/postorius/locale/crh/LC_MESSAGES creating build/lib/postorius/locale/cs creating build/lib/postorius/locale/cs/LC_MESSAGES copying src/postorius/locale/cs/LC_MESSAGES/django.po -> build/lib/postorius/locale/cs/LC_MESSAGES creating build/lib/postorius/locale/cv creating build/lib/postorius/locale/cv/LC_MESSAGES copying src/postorius/locale/cv/LC_MESSAGES/django.po -> build/lib/postorius/locale/cv/LC_MESSAGES creating build/lib/postorius/locale/cy creating build/lib/postorius/locale/cy/LC_MESSAGES copying src/postorius/locale/cy/LC_MESSAGES/django.po -> build/lib/postorius/locale/cy/LC_MESSAGES creating build/lib/postorius/locale/da creating build/lib/postorius/locale/da/LC_MESSAGES copying src/postorius/locale/da/LC_MESSAGES/django.po -> build/lib/postorius/locale/da/LC_MESSAGES creating build/lib/postorius/locale/de creating build/lib/postorius/locale/de/LC_MESSAGES copying src/postorius/locale/de/LC_MESSAGES/django.po -> build/lib/postorius/locale/de/LC_MESSAGES creating build/lib/postorius/locale/el creating build/lib/postorius/locale/el/LC_MESSAGES copying src/postorius/locale/el/LC_MESSAGES/django.po -> build/lib/postorius/locale/el/LC_MESSAGES creating build/lib/postorius/locale/en_AU creating build/lib/postorius/locale/en_AU/LC_MESSAGES copying src/postorius/locale/en_AU/LC_MESSAGES/django.po -> build/lib/postorius/locale/en_AU/LC_MESSAGES creating build/lib/postorius/locale/en_CA creating build/lib/postorius/locale/en_CA/LC_MESSAGES copying src/postorius/locale/en_CA/LC_MESSAGES/django.po -> build/lib/postorius/locale/en_CA/LC_MESSAGES creating build/lib/postorius/locale/en_GB creating build/lib/postorius/locale/en_GB/LC_MESSAGES copying src/postorius/locale/en_GB/LC_MESSAGES/django.po -> build/lib/postorius/locale/en_GB/LC_MESSAGES creating build/lib/postorius/locale/eo creating build/lib/postorius/locale/eo/LC_MESSAGES copying src/postorius/locale/eo/LC_MESSAGES/django.po -> build/lib/postorius/locale/eo/LC_MESSAGES creating build/lib/postorius/locale/es creating build/lib/postorius/locale/es/LC_MESSAGES copying src/postorius/locale/es/LC_MESSAGES/django.po -> build/lib/postorius/locale/es/LC_MESSAGES creating build/lib/postorius/locale/et creating build/lib/postorius/locale/et/LC_MESSAGES copying src/postorius/locale/et/LC_MESSAGES/django.po -> build/lib/postorius/locale/et/LC_MESSAGES creating build/lib/postorius/locale/eu creating build/lib/postorius/locale/eu/LC_MESSAGES copying src/postorius/locale/eu/LC_MESSAGES/django.po -> build/lib/postorius/locale/eu/LC_MESSAGES creating build/lib/postorius/locale/fa creating build/lib/postorius/locale/fa/LC_MESSAGES copying src/postorius/locale/fa/LC_MESSAGES/django.po -> build/lib/postorius/locale/fa/LC_MESSAGES creating build/lib/postorius/locale/fi creating build/lib/postorius/locale/fi/LC_MESSAGES copying src/postorius/locale/fi/LC_MESSAGES/django.po -> build/lib/postorius/locale/fi/LC_MESSAGES creating build/lib/postorius/locale/fil creating build/lib/postorius/locale/fil/LC_MESSAGES copying src/postorius/locale/fil/LC_MESSAGES/django.po -> build/lib/postorius/locale/fil/LC_MESSAGES creating build/lib/postorius/locale/fo creating build/lib/postorius/locale/fo/LC_MESSAGES copying src/postorius/locale/fo/LC_MESSAGES/django.po -> build/lib/postorius/locale/fo/LC_MESSAGES creating build/lib/postorius/locale/fr creating build/lib/postorius/locale/fr/LC_MESSAGES copying src/postorius/locale/fr/LC_MESSAGES/django.po -> build/lib/postorius/locale/fr/LC_MESSAGES creating build/lib/postorius/locale/fr_CA creating build/lib/postorius/locale/fr_CA/LC_MESSAGES copying src/postorius/locale/fr_CA/LC_MESSAGES/django.po -> build/lib/postorius/locale/fr_CA/LC_MESSAGES creating build/lib/postorius/locale/frp creating build/lib/postorius/locale/frp/LC_MESSAGES copying src/postorius/locale/frp/LC_MESSAGES/django.po -> build/lib/postorius/locale/frp/LC_MESSAGES creating build/lib/postorius/locale/fy creating build/lib/postorius/locale/fy/LC_MESSAGES copying src/postorius/locale/fy/LC_MESSAGES/django.po -> build/lib/postorius/locale/fy/LC_MESSAGES creating build/lib/postorius/locale/ga creating build/lib/postorius/locale/ga/LC_MESSAGES copying src/postorius/locale/ga/LC_MESSAGES/django.po -> build/lib/postorius/locale/ga/LC_MESSAGES creating build/lib/postorius/locale/gd creating build/lib/postorius/locale/gd/LC_MESSAGES copying src/postorius/locale/gd/LC_MESSAGES/django.po -> build/lib/postorius/locale/gd/LC_MESSAGES creating build/lib/postorius/locale/gl creating build/lib/postorius/locale/gl/LC_MESSAGES copying src/postorius/locale/gl/LC_MESSAGES/django.po -> build/lib/postorius/locale/gl/LC_MESSAGES creating build/lib/postorius/locale/gu creating build/lib/postorius/locale/gu/LC_MESSAGES copying src/postorius/locale/gu/LC_MESSAGES/django.po -> build/lib/postorius/locale/gu/LC_MESSAGES creating build/lib/postorius/locale/he creating build/lib/postorius/locale/he/LC_MESSAGES copying src/postorius/locale/he/LC_MESSAGES/django.po -> build/lib/postorius/locale/he/LC_MESSAGES creating build/lib/postorius/locale/hi creating build/lib/postorius/locale/hi/LC_MESSAGES copying src/postorius/locale/hi/LC_MESSAGES/django.po -> build/lib/postorius/locale/hi/LC_MESSAGES creating build/lib/postorius/locale/hr creating build/lib/postorius/locale/hr/LC_MESSAGES copying src/postorius/locale/hr/LC_MESSAGES/django.po -> build/lib/postorius/locale/hr/LC_MESSAGES creating build/lib/postorius/locale/ht creating build/lib/postorius/locale/ht/LC_MESSAGES copying src/postorius/locale/ht/LC_MESSAGES/django.po -> build/lib/postorius/locale/ht/LC_MESSAGES creating build/lib/postorius/locale/hu creating build/lib/postorius/locale/hu/LC_MESSAGES copying src/postorius/locale/hu/LC_MESSAGES/django.po -> build/lib/postorius/locale/hu/LC_MESSAGES creating build/lib/postorius/locale/hy creating build/lib/postorius/locale/hy/LC_MESSAGES copying src/postorius/locale/hy/LC_MESSAGES/django.po -> build/lib/postorius/locale/hy/LC_MESSAGES creating build/lib/postorius/locale/ia creating build/lib/postorius/locale/ia/LC_MESSAGES copying src/postorius/locale/ia/LC_MESSAGES/django.po -> build/lib/postorius/locale/ia/LC_MESSAGES creating build/lib/postorius/locale/id creating build/lib/postorius/locale/id/LC_MESSAGES copying src/postorius/locale/id/LC_MESSAGES/django.po -> build/lib/postorius/locale/id/LC_MESSAGES creating build/lib/postorius/locale/is creating build/lib/postorius/locale/is/LC_MESSAGES copying src/postorius/locale/is/LC_MESSAGES/django.po -> build/lib/postorius/locale/is/LC_MESSAGES creating build/lib/postorius/locale/it creating build/lib/postorius/locale/it/LC_MESSAGES copying src/postorius/locale/it/LC_MESSAGES/django.po -> build/lib/postorius/locale/it/LC_MESSAGES creating build/lib/postorius/locale/ja creating build/lib/postorius/locale/ja/LC_MESSAGES copying src/postorius/locale/ja/LC_MESSAGES/django.po -> build/lib/postorius/locale/ja/LC_MESSAGES creating build/lib/postorius/locale/ka creating build/lib/postorius/locale/ka/LC_MESSAGES copying src/postorius/locale/ka/LC_MESSAGES/django.po -> build/lib/postorius/locale/ka/LC_MESSAGES creating build/lib/postorius/locale/kk creating build/lib/postorius/locale/kk/LC_MESSAGES copying src/postorius/locale/kk/LC_MESSAGES/django.po -> build/lib/postorius/locale/kk/LC_MESSAGES creating build/lib/postorius/locale/kl creating build/lib/postorius/locale/kl/LC_MESSAGES copying src/postorius/locale/kl/LC_MESSAGES/django.po -> build/lib/postorius/locale/kl/LC_MESSAGES creating build/lib/postorius/locale/km creating build/lib/postorius/locale/km/LC_MESSAGES copying src/postorius/locale/km/LC_MESSAGES/django.po -> build/lib/postorius/locale/km/LC_MESSAGES creating build/lib/postorius/locale/kn creating build/lib/postorius/locale/kn/LC_MESSAGES copying src/postorius/locale/kn/LC_MESSAGES/django.po -> build/lib/postorius/locale/kn/LC_MESSAGES creating build/lib/postorius/locale/ko creating build/lib/postorius/locale/ko/LC_MESSAGES copying src/postorius/locale/ko/LC_MESSAGES/django.po -> build/lib/postorius/locale/ko/LC_MESSAGES creating build/lib/postorius/locale/ku creating build/lib/postorius/locale/ku/LC_MESSAGES copying src/postorius/locale/ku/LC_MESSAGES/django.po -> build/lib/postorius/locale/ku/LC_MESSAGES creating build/lib/postorius/locale/kw creating build/lib/postorius/locale/kw/LC_MESSAGES copying src/postorius/locale/kw/LC_MESSAGES/django.po -> build/lib/postorius/locale/kw/LC_MESSAGES creating build/lib/postorius/locale/ky creating build/lib/postorius/locale/ky/LC_MESSAGES copying src/postorius/locale/ky/LC_MESSAGES/django.po -> build/lib/postorius/locale/ky/LC_MESSAGES creating build/lib/postorius/locale/la creating build/lib/postorius/locale/la/LC_MESSAGES copying src/postorius/locale/la/LC_MESSAGES/django.po -> build/lib/postorius/locale/la/LC_MESSAGES creating build/lib/postorius/locale/lb creating build/lib/postorius/locale/lb/LC_MESSAGES copying src/postorius/locale/lb/LC_MESSAGES/django.po -> build/lib/postorius/locale/lb/LC_MESSAGES creating build/lib/postorius/locale/lo creating build/lib/postorius/locale/lo/LC_MESSAGES copying src/postorius/locale/lo/LC_MESSAGES/django.po -> build/lib/postorius/locale/lo/LC_MESSAGES creating build/lib/postorius/locale/lt creating build/lib/postorius/locale/lt/LC_MESSAGES copying src/postorius/locale/lt/LC_MESSAGES/django.po -> build/lib/postorius/locale/lt/LC_MESSAGES creating build/lib/postorius/locale/lv creating build/lib/postorius/locale/lv/LC_MESSAGES copying src/postorius/locale/lv/LC_MESSAGES/django.po -> build/lib/postorius/locale/lv/LC_MESSAGES creating build/lib/postorius/locale/mg creating build/lib/postorius/locale/mg/LC_MESSAGES copying src/postorius/locale/mg/LC_MESSAGES/django.po -> build/lib/postorius/locale/mg/LC_MESSAGES creating build/lib/postorius/locale/mhr creating build/lib/postorius/locale/mhr/LC_MESSAGES copying src/postorius/locale/mhr/LC_MESSAGES/django.po -> build/lib/postorius/locale/mhr/LC_MESSAGES creating build/lib/postorius/locale/mi creating build/lib/postorius/locale/mi/LC_MESSAGES copying src/postorius/locale/mi/LC_MESSAGES/django.po -> build/lib/postorius/locale/mi/LC_MESSAGES creating build/lib/postorius/locale/ml creating build/lib/postorius/locale/ml/LC_MESSAGES copying src/postorius/locale/ml/LC_MESSAGES/django.po -> build/lib/postorius/locale/ml/LC_MESSAGES creating build/lib/postorius/locale/mr creating build/lib/postorius/locale/mr/LC_MESSAGES copying src/postorius/locale/mr/LC_MESSAGES/django.po -> build/lib/postorius/locale/mr/LC_MESSAGES creating build/lib/postorius/locale/ms creating build/lib/postorius/locale/ms/LC_MESSAGES copying src/postorius/locale/ms/LC_MESSAGES/django.po -> build/lib/postorius/locale/ms/LC_MESSAGES creating build/lib/postorius/locale/my creating build/lib/postorius/locale/my/LC_MESSAGES copying src/postorius/locale/my/LC_MESSAGES/django.po -> build/lib/postorius/locale/my/LC_MESSAGES creating build/lib/postorius/locale/nb_NO creating build/lib/postorius/locale/nb_NO/LC_MESSAGES copying src/postorius/locale/nb_NO/LC_MESSAGES/django.po -> build/lib/postorius/locale/nb_NO/LC_MESSAGES creating build/lib/postorius/locale/ne creating build/lib/postorius/locale/ne/LC_MESSAGES copying src/postorius/locale/ne/LC_MESSAGES/django.po -> build/lib/postorius/locale/ne/LC_MESSAGES creating build/lib/postorius/locale/nl creating build/lib/postorius/locale/nl/LC_MESSAGES copying src/postorius/locale/nl/LC_MESSAGES/django.po -> build/lib/postorius/locale/nl/LC_MESSAGES creating build/lib/postorius/locale/nn_NO creating build/lib/postorius/locale/nn_NO/LC_MESSAGES copying src/postorius/locale/nn_NO/LC_MESSAGES/django.po -> build/lib/postorius/locale/nn_NO/LC_MESSAGES creating build/lib/postorius/locale/oc creating build/lib/postorius/locale/oc/LC_MESSAGES copying src/postorius/locale/oc/LC_MESSAGES/django.po -> build/lib/postorius/locale/oc/LC_MESSAGES creating build/lib/postorius/locale/os creating build/lib/postorius/locale/os/LC_MESSAGES copying src/postorius/locale/os/LC_MESSAGES/django.po -> build/lib/postorius/locale/os/LC_MESSAGES creating build/lib/postorius/locale/pa creating build/lib/postorius/locale/pa/LC_MESSAGES copying src/postorius/locale/pa/LC_MESSAGES/django.po -> build/lib/postorius/locale/pa/LC_MESSAGES creating build/lib/postorius/locale/pl creating build/lib/postorius/locale/pl/LC_MESSAGES copying src/postorius/locale/pl/LC_MESSAGES/django.po -> build/lib/postorius/locale/pl/LC_MESSAGES creating build/lib/postorius/locale/ps creating build/lib/postorius/locale/ps/LC_MESSAGES copying src/postorius/locale/ps/LC_MESSAGES/django.po -> build/lib/postorius/locale/ps/LC_MESSAGES creating build/lib/postorius/locale/pt creating build/lib/postorius/locale/pt/LC_MESSAGES copying src/postorius/locale/pt/LC_MESSAGES/django.po -> build/lib/postorius/locale/pt/LC_MESSAGES creating build/lib/postorius/locale/pt_BR creating build/lib/postorius/locale/pt_BR/LC_MESSAGES copying src/postorius/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/postorius/locale/pt_BR/LC_MESSAGES creating build/lib/postorius/locale/ro creating build/lib/postorius/locale/ro/LC_MESSAGES copying src/postorius/locale/ro/LC_MESSAGES/django.po -> build/lib/postorius/locale/ro/LC_MESSAGES creating build/lib/postorius/locale/ru creating build/lib/postorius/locale/ru/LC_MESSAGES copying src/postorius/locale/ru/LC_MESSAGES/django.po -> build/lib/postorius/locale/ru/LC_MESSAGES creating build/lib/postorius/locale/sa creating build/lib/postorius/locale/sa/LC_MESSAGES copying src/postorius/locale/sa/LC_MESSAGES/django.po -> build/lib/postorius/locale/sa/LC_MESSAGES creating build/lib/postorius/locale/sc creating build/lib/postorius/locale/sc/LC_MESSAGES copying src/postorius/locale/sc/LC_MESSAGES/django.po -> build/lib/postorius/locale/sc/LC_MESSAGES creating build/lib/postorius/locale/sd creating build/lib/postorius/locale/sd/LC_MESSAGES copying src/postorius/locale/sd/LC_MESSAGES/django.po -> build/lib/postorius/locale/sd/LC_MESSAGES creating build/lib/postorius/locale/se creating build/lib/postorius/locale/se/LC_MESSAGES copying src/postorius/locale/se/LC_MESSAGES/django.po -> build/lib/postorius/locale/se/LC_MESSAGES creating build/lib/postorius/locale/shn creating build/lib/postorius/locale/shn/LC_MESSAGES copying src/postorius/locale/shn/LC_MESSAGES/django.po -> build/lib/postorius/locale/shn/LC_MESSAGES creating build/lib/postorius/locale/si creating build/lib/postorius/locale/si/LC_MESSAGES copying src/postorius/locale/si/LC_MESSAGES/django.po -> build/lib/postorius/locale/si/LC_MESSAGES creating build/lib/postorius/locale/sk creating build/lib/postorius/locale/sk/LC_MESSAGES copying src/postorius/locale/sk/LC_MESSAGES/django.po -> build/lib/postorius/locale/sk/LC_MESSAGES creating build/lib/postorius/locale/sl creating build/lib/postorius/locale/sl/LC_MESSAGES copying src/postorius/locale/sl/LC_MESSAGES/django.po -> build/lib/postorius/locale/sl/LC_MESSAGES creating build/lib/postorius/locale/sq creating build/lib/postorius/locale/sq/LC_MESSAGES copying src/postorius/locale/sq/LC_MESSAGES/django.po -> build/lib/postorius/locale/sq/LC_MESSAGES creating build/lib/postorius/locale/sr creating build/lib/postorius/locale/sr/LC_MESSAGES copying src/postorius/locale/sr/LC_MESSAGES/django.po -> build/lib/postorius/locale/sr/LC_MESSAGES creating build/lib/postorius/locale/sv creating build/lib/postorius/locale/sv/LC_MESSAGES copying src/postorius/locale/sv/LC_MESSAGES/django.po -> build/lib/postorius/locale/sv/LC_MESSAGES creating build/lib/postorius/locale/sw creating build/lib/postorius/locale/sw/LC_MESSAGES copying src/postorius/locale/sw/LC_MESSAGES/django.po -> build/lib/postorius/locale/sw/LC_MESSAGES creating build/lib/postorius/locale/szl creating build/lib/postorius/locale/szl/LC_MESSAGES copying src/postorius/locale/szl/LC_MESSAGES/django.po -> build/lib/postorius/locale/szl/LC_MESSAGES creating build/lib/postorius/locale/ta creating build/lib/postorius/locale/ta/LC_MESSAGES copying src/postorius/locale/ta/LC_MESSAGES/django.po -> build/lib/postorius/locale/ta/LC_MESSAGES creating build/lib/postorius/locale/te creating build/lib/postorius/locale/te/LC_MESSAGES copying src/postorius/locale/te/LC_MESSAGES/django.po -> build/lib/postorius/locale/te/LC_MESSAGES creating build/lib/postorius/locale/tg creating build/lib/postorius/locale/tg/LC_MESSAGES copying src/postorius/locale/tg/LC_MESSAGES/django.po -> build/lib/postorius/locale/tg/LC_MESSAGES creating build/lib/postorius/locale/th creating build/lib/postorius/locale/th/LC_MESSAGES copying src/postorius/locale/th/LC_MESSAGES/django.po -> build/lib/postorius/locale/th/LC_MESSAGES creating build/lib/postorius/locale/ti creating build/lib/postorius/locale/ti/LC_MESSAGES copying src/postorius/locale/ti/LC_MESSAGES/django.po -> build/lib/postorius/locale/ti/LC_MESSAGES creating build/lib/postorius/locale/tr creating build/lib/postorius/locale/tr/LC_MESSAGES copying src/postorius/locale/tr/LC_MESSAGES/django.po -> build/lib/postorius/locale/tr/LC_MESSAGES creating build/lib/postorius/locale/ug creating build/lib/postorius/locale/ug/LC_MESSAGES copying src/postorius/locale/ug/LC_MESSAGES/django.po -> build/lib/postorius/locale/ug/LC_MESSAGES creating build/lib/postorius/locale/uk creating build/lib/postorius/locale/uk/LC_MESSAGES copying src/postorius/locale/uk/LC_MESSAGES/django.po -> build/lib/postorius/locale/uk/LC_MESSAGES creating build/lib/postorius/locale/ur creating build/lib/postorius/locale/ur/LC_MESSAGES copying src/postorius/locale/ur/LC_MESSAGES/django.po -> build/lib/postorius/locale/ur/LC_MESSAGES creating build/lib/postorius/locale/uz creating build/lib/postorius/locale/uz/LC_MESSAGES copying src/postorius/locale/uz/LC_MESSAGES/django.po -> build/lib/postorius/locale/uz/LC_MESSAGES creating build/lib/postorius/locale/vi creating build/lib/postorius/locale/vi/LC_MESSAGES copying src/postorius/locale/vi/LC_MESSAGES/django.po -> build/lib/postorius/locale/vi/LC_MESSAGES creating build/lib/postorius/locale/wae creating build/lib/postorius/locale/wae/LC_MESSAGES copying src/postorius/locale/wae/LC_MESSAGES/django.po -> build/lib/postorius/locale/wae/LC_MESSAGES creating build/lib/postorius/locale/zh_CN creating build/lib/postorius/locale/zh_CN/LC_MESSAGES copying src/postorius/locale/zh_CN/LC_MESSAGES/django.po -> build/lib/postorius/locale/zh_CN/LC_MESSAGES creating build/lib/postorius/locale/zh_HK creating build/lib/postorius/locale/zh_HK/LC_MESSAGES copying src/postorius/locale/zh_HK/LC_MESSAGES/django.po -> build/lib/postorius/locale/zh_HK/LC_MESSAGES creating build/lib/postorius/locale/zh_TW creating build/lib/postorius/locale/zh_TW/LC_MESSAGES copying src/postorius/locale/zh_TW/LC_MESSAGES/django.po -> build/lib/postorius/locale/zh_TW/LC_MESSAGES creating build/lib/postorius/static creating build/lib/postorius/static/postorius creating build/lib/postorius/static/postorius/css copying src/postorius/static/postorius/css/style.css -> build/lib/postorius/static/postorius/css creating build/lib/postorius/static/postorius/img copying src/postorius/static/postorius/img/favicon.ico -> build/lib/postorius/static/postorius/img copying src/postorius/static/postorius/img/mailman_logo.png -> build/lib/postorius/static/postorius/img copying src/postorius/static/postorius/img/mailman_logo_small_trans.png -> build/lib/postorius/static/postorius/img copying src/postorius/static/postorius/img/mailman_logo_trans.png -> build/lib/postorius/static/postorius/img creating build/lib/postorius/static/postorius/js copying src/postorius/static/postorius/js/held_messages.js -> build/lib/postorius/static/postorius/js copying src/postorius/static/postorius/js/script.js -> build/lib/postorius/static/postorius/js creating build/lib/postorius/static/postorius/libs creating build/lib/postorius/static/postorius/libs/bootstrap creating build/lib/postorius/static/postorius/libs/bootstrap/css copying src/postorius/static/postorius/libs/bootstrap/css/bootstrap.min.css -> build/lib/postorius/static/postorius/libs/bootstrap/css copying src/postorius/static/postorius/libs/bootstrap/css/bootstrap.min.css.map -> build/lib/postorius/static/postorius/libs/bootstrap/css creating build/lib/postorius/static/postorius/libs/bootstrap/fonts copying src/postorius/static/postorius/libs/bootstrap/fonts/glyphicons-halflings-regular.eot -> build/lib/postorius/static/postorius/libs/bootstrap/fonts copying src/postorius/static/postorius/libs/bootstrap/fonts/glyphicons-halflings-regular.svg -> build/lib/postorius/static/postorius/libs/bootstrap/fonts copying src/postorius/static/postorius/libs/bootstrap/fonts/glyphicons-halflings-regular.ttf -> build/lib/postorius/static/postorius/libs/bootstrap/fonts copying src/postorius/static/postorius/libs/bootstrap/fonts/glyphicons-halflings-regular.woff -> build/lib/postorius/static/postorius/libs/bootstrap/fonts copying src/postorius/static/postorius/libs/bootstrap/fonts/glyphicons-halflings-regular.woff2 -> build/lib/postorius/static/postorius/libs/bootstrap/fonts creating build/lib/postorius/static/postorius/libs/bootstrap/js copying src/postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.js -> build/lib/postorius/static/postorius/libs/bootstrap/js copying src/postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.js.map -> build/lib/postorius/static/postorius/libs/bootstrap/js copying src/postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js -> build/lib/postorius/static/postorius/libs/bootstrap/js copying src/postorius/static/postorius/libs/bootstrap/js/bootstrap.bundle.min.js.map -> build/lib/postorius/static/postorius/libs/bootstrap/js creating build/lib/postorius/static/postorius/libs/fonts creating build/lib/postorius/static/postorius/libs/fonts/font-awesome copying src/postorius/static/postorius/libs/fonts/font-awesome/VERSION.txt -> build/lib/postorius/static/postorius/libs/fonts/font-awesome creating build/lib/postorius/static/postorius/libs/fonts/font-awesome/css copying src/postorius/static/postorius/libs/fonts/font-awesome/css/font-awesome.css -> build/lib/postorius/static/postorius/libs/fonts/font-awesome/css copying src/postorius/static/postorius/libs/fonts/font-awesome/css/font-awesome.min.css -> build/lib/postorius/static/postorius/libs/fonts/font-awesome/css creating build/lib/postorius/static/postorius/libs/fonts/font-awesome/fonts copying src/postorius/static/postorius/libs/fonts/font-awesome/fonts/FontAwesome.otf -> build/lib/postorius/static/postorius/libs/fonts/font-awesome/fonts copying src/postorius/static/postorius/libs/fonts/font-awesome/fonts/fontawesome-webfont.eot -> build/lib/postorius/static/postorius/libs/fonts/font-awesome/fonts copying src/postorius/static/postorius/libs/fonts/font-awesome/fonts/fontawesome-webfont.svg -> build/lib/postorius/static/postorius/libs/fonts/font-awesome/fonts copying src/postorius/static/postorius/libs/fonts/font-awesome/fonts/fontawesome-webfont.ttf -> build/lib/postorius/static/postorius/libs/fonts/font-awesome/fonts copying src/postorius/static/postorius/libs/fonts/font-awesome/fonts/fontawesome-webfont.woff -> build/lib/postorius/static/postorius/libs/fonts/font-awesome/fonts copying src/postorius/static/postorius/libs/fonts/font-awesome/fonts/fontawesome-webfont.woff2 -> build/lib/postorius/static/postorius/libs/fonts/font-awesome/fonts creating build/lib/postorius/static/postorius/libs/jquery copying src/postorius/static/postorius/libs/jquery/jquery-3.6.0.js -> build/lib/postorius/static/postorius/libs/jquery copying src/postorius/static/postorius/libs/jquery/jquery-3.6.0.min.js -> build/lib/postorius/static/postorius/libs/jquery copying src/postorius/static/postorius/libs/jquery/jquery-3.6.0.min.map -> build/lib/postorius/static/postorius/libs/jquery creating build/lib/postorius/templates copying src/postorius/templates/403.html -> build/lib/postorius/templates copying src/postorius/templates/404.html -> build/lib/postorius/templates copying src/postorius/templates/500.html -> build/lib/postorius/templates creating build/lib/postorius/templates/account copying src/postorius/templates/account/base.html -> build/lib/postorius/templates/account creating build/lib/postorius/templates/django_mailman3 copying src/postorius/templates/django_mailman3/base.html -> build/lib/postorius/templates/django_mailman3 creating build/lib/postorius/templates/postorius copying src/postorius/templates/postorius/bans.html -> build/lib/postorius/templates/postorius copying src/postorius/templates/postorius/base.html -> build/lib/postorius/templates/postorius copying src/postorius/templates/postorius/index.html -> build/lib/postorius/templates/postorius copying src/postorius/templates/postorius/system_information.html -> build/lib/postorius/templates/postorius creating build/lib/postorius/templates/postorius/domain copying src/postorius/templates/postorius/domain/confirm_delete.html -> build/lib/postorius/templates/postorius/domain copying src/postorius/templates/postorius/domain/edit.html -> build/lib/postorius/templates/postorius/domain copying src/postorius/templates/postorius/domain/index.html -> build/lib/postorius/templates/postorius/domain copying src/postorius/templates/postorius/domain/new.html -> build/lib/postorius/templates/postorius/domain copying src/postorius/templates/postorius/domain/owners.html -> build/lib/postorius/templates/postorius/domain copying src/postorius/templates/postorius/domain/template_add.html -> build/lib/postorius/templates/postorius/domain copying src/postorius/templates/postorius/domain/template_delete.html -> build/lib/postorius/templates/postorius/domain copying src/postorius/templates/postorius/domain/template_index.html -> build/lib/postorius/templates/postorius/domain creating build/lib/postorius/templates/postorius/errors copying src/postorius/templates/postorius/errors/generic.html -> build/lib/postorius/templates/postorius/errors creating build/lib/postorius/templates/postorius/fragments copying src/postorius/templates/postorius/fragments/bans.html -> build/lib/postorius/templates/postorius/fragments creating build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/bans.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/confirm_delete.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/confirm_remove_role.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/confirm_removeall_subscribers.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/confirm_token.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/header_matches.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/held_messages.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/mass_removal.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/mass_subscribe.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/memberoptions.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/members.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/new.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/pending_confirmations.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/settings.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/subscription_requests.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/summary.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/template_add.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/template_delete.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/template_list.html -> build/lib/postorius/templates/postorius/lists copying src/postorius/templates/postorius/lists/template_update.html -> build/lib/postorius/templates/postorius/lists creating build/lib/postorius/templates/postorius/menu copying src/postorius/templates/postorius/menu/list_nav.html -> build/lib/postorius/templates/postorius/menu copying src/postorius/templates/postorius/menu/user_nav.html -> build/lib/postorius/templates/postorius/menu creating build/lib/postorius/templates/postorius/user copying src/postorius/templates/postorius/user/address_preferences.html -> build/lib/postorius/templates/postorius/user copying src/postorius/templates/postorius/user/all.html -> build/lib/postorius/templates/postorius/user copying src/postorius/templates/postorius/user/confirm_delete.html -> build/lib/postorius/templates/postorius/user copying src/postorius/templates/postorius/user/list_options.html -> build/lib/postorius/templates/postorius/user copying src/postorius/templates/postorius/user/mailman_settings.html -> build/lib/postorius/templates/postorius/user copying src/postorius/templates/postorius/user/manage.html -> build/lib/postorius/templates/postorius/user copying src/postorius/templates/postorius/user/subscription_preferences.html -> build/lib/postorius/templates/postorius/user copying src/postorius/templates/postorius/user/subscriptions.html -> build/lib/postorius/templates/postorius/user copying src/postorius/doc/Makefile -> build/lib/postorius/doc copying src/postorius/doc/deployment.rst -> build/lib/postorius/doc copying src/postorius/doc/development.rst -> build/lib/postorius/doc copying src/postorius/doc/index.rst -> build/lib/postorius/doc copying src/postorius/doc/news.rst -> build/lib/postorius/doc copying src/postorius/doc/setup.rst -> build/lib/postorius/doc creating build/lib/postorius/tests/test_data copying src/postorius/tests/test_data/bad-email.txt -> build/lib/postorius/tests/test_data copying src/postorius/tests/test_data/simple-email.txt -> build/lib/postorius/tests/test_data copying src/postorius/tests/test_data/test-email-attachment.txt -> build/lib/postorius/tests/test_data copying src/postorius/tests/test_data/test-held-message-1.txt -> build/lib/postorius/tests/test_data