D: [iurt_root_command] chroot Building target platforms: noarch Building for target noarch Installing /home/pterjan/rpmbuild/SRPMS/python-django-contrib-comments-2.2.0-5.mga10.src.rpm Executing(%mkbuilddir): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.oJOsVX Executing(%prep): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.FWI4s1 + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + cd /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build + rm -rf django-contrib-comments-2.2.0 + /usr/lib/rpm/rpmuncompress -x /home/pterjan/rpmbuild/SOURCES/django-contrib-comments-2.2.0.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd django-contrib-comments-2.2.0 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + /usr/lib/rpm/rpmuncompress /home/pterjan/rpmbuild/SOURCES/36bd49060c58eb96e12e42eb098eb63ccaae848e.patch + /usr/bin/patch -p1 -s --fuzz=0 --no-backup-if-mismatch -f + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.f8gAg7 + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build + cd django-contrib-comments-2.2.0 + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(packaging)' + echo 'python3dist(pip) >= 19' + '[' -f pyproject.toml ']' + '[' -f setup.py ']' + echo 'python3dist(setuptools) >= 40.8' + for f in pyproject.toml setup.py setup.cfg + '[' -f pyproject.toml ']' + for f in pyproject.toml setup.py setup.cfg + '[' -f setup.py ']' + sed -i -E -e '/^requires/s/(['\''"]\s*flit_core\s*>=\s*[0-9]+(\.[0-9]+)+)\s*,\s*<\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\4/' setup.py + sed -i -E -e '/python_requires/s/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/' setup.py + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9a-z]+)*)\s*,\s*(<|!=|<=)\s*[0-9]+(\.[0-9a-z]+)*(-?dev[0-9]*)?(\.\*)*(\s*['\''"]?)/\1\7/g' setup.py + sed -i -E -e 's/(['\''"]\w+\s*)!=(\s*([0-9])+(\.[0-9]+)*\s*['\''"])/\1>\2/g' setup.py + sed -i -E -e 's/(['\''"]\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\5/g' setup.py + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/g' setup.py + sed -i -E -e 's/(['\''"]\s*)\^(\s*[0-9]+(\.[0-9]+)*\s*['\''"])/\1>=\2/g' setup.py + sed -i -e 's/~=/>=/g' setup.py + sed -i -E -e 's/(['\''"]\s*\S*\s*)==(\s*[0-9]+(\.[0-9]+)*)\.\*(\s*['\''"])/\1>=\2\4/g' setup.py + sed -i -E -e 's/(['\''"]?\w*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)[0-9]+(\.[0-9]+)*\s*(['\''"]?)/\1\5/g' setup.py + for f in pyproject.toml setup.py setup.cfg + '[' -f setup.cfg ']' + sed -i -E -e '/^requires/s/(['\''"]\s*flit_core\s*>=\s*[0-9]+(\.[0-9]+)+)\s*,\s*<\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\4/' setup.cfg + sed -i -E -e '/python_requires/s/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/' setup.cfg + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9a-z]+)*)\s*,\s*(<|!=|<=)\s*[0-9]+(\.[0-9a-z]+)*(-?dev[0-9]*)?(\.\*)*(\s*['\''"]?)/\1\7/g' setup.cfg + sed -i -E -e 's/(['\''"]\w+\s*)!=(\s*([0-9])+(\.[0-9]+)*\s*['\''"])/\1>\2/g' setup.cfg + sed -i -E -e 's/(['\''"]\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\5/g' setup.cfg + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/g' setup.cfg + sed -i -E -e 's/(['\''"]\s*)\^(\s*[0-9]+(\.[0-9]+)*\s*['\''"])/\1>=\2/g' setup.cfg + sed -i -e 's/~=/>=/g' setup.cfg + sed -i -E -e 's/(['\''"]\s*\S*\s*)==(\s*[0-9]+(\.[0-9]+)*)\.\*(\s*['\''"])/\1>=\2\4/g' setup.cfg + sed -i -E -e 's/(['\''"]?\w*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)[0-9]+(\.[0-9]+)*\s*(['\''"]?)/\1\5/g' setup.cfg + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir + echo -n + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + VALAFLAGS=-g + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + CXX=g++ + TMPDIR=/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir + RPM_TOXENV=py313 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/pyproject-wheeldir --output /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/python-django-contrib-comments-2.2.0-5.mga10.noarch-pyproject-buildrequires Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 78.1.0) /usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running egg_info writing django_contrib_comments.egg-info/PKG-INFO writing dependency_links to django_contrib_comments.egg-info/dependency_links.txt writing requirements to django_contrib_comments.egg-info/requires.txt writing top-level names to django_contrib_comments.egg-info/top_level.txt reading manifest file 'django_contrib_comments.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '__pycache__' found under directory '*' warning: no previously-included files matching '*.py[co]' found under directory '*' adding license file 'LICENSE.txt' writing manifest file 'django_contrib_comments.egg-info/SOURCES.txt' running dist_info writing django_contrib_comments.egg-info/PKG-INFO writing dependency_links to django_contrib_comments.egg-info/dependency_links.txt writing requirements to django_contrib_comments.egg-info/requires.txt writing top-level names to django_contrib_comments.egg-info/top_level.txt reading manifest file 'django_contrib_comments.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '__pycache__' found under directory '*' warning: no previously-included files matching '*.py[co]' found under directory '*' adding license file 'LICENSE.txt' writing manifest file 'django_contrib_comments.egg-info/SOURCES.txt' creating '/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/django_contrib_comments-2.2.0.dist-info' Handling Django>=2.2 from hook generated metadata: Requires-Dist (django-contrib-comments) Requirement satisfied: Django>=2.2 (installed: Django 5.1.7) + cat /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/python-django-contrib-comments-2.2.0-5.mga10.noarch-pyproject-buildrequires + rm -rfv django_contrib_comments-2.2.0.dist-info/ removed 'django_contrib_comments-2.2.0.dist-info/top_level.txt' removed 'django_contrib_comments-2.2.0.dist-info/METADATA' removed 'django_contrib_comments-2.2.0.dist-info/licenses/LICENSE.txt' removed directory 'django_contrib_comments-2.2.0.dist-info/licenses' removed directory 'django_contrib_comments-2.2.0.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.DjiOWA + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd django-contrib-comments-2.2.0 + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + mkdir -p /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + VALAFLAGS=-g + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + CXX=g++ + TMPDIR=/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_wheel.py /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/pyproject-wheeldir Processing /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0 Preparing metadata (pyproject.toml): started Running command Preparing metadata (pyproject.toml) /usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running dist_info creating /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir/pip-modern-metadata-v0_l2fuf/django_contrib_comments.egg-info writing /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir/pip-modern-metadata-v0_l2fuf/django_contrib_comments.egg-info/PKG-INFO writing dependency_links to /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir/pip-modern-metadata-v0_l2fuf/django_contrib_comments.egg-info/dependency_links.txt writing requirements to /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir/pip-modern-metadata-v0_l2fuf/django_contrib_comments.egg-info/requires.txt writing top-level names to /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir/pip-modern-metadata-v0_l2fuf/django_contrib_comments.egg-info/top_level.txt writing manifest file '/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir/pip-modern-metadata-v0_l2fuf/django_contrib_comments.egg-info/SOURCES.txt' reading manifest file '/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir/pip-modern-metadata-v0_l2fuf/django_contrib_comments.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '__pycache__' found under directory '*' warning: no previously-included files matching '*.py[co]' found under directory '*' adding license file 'LICENSE.txt' writing manifest file '/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir/pip-modern-metadata-v0_l2fuf/django_contrib_comments.egg-info/SOURCES.txt' creating '/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir/pip-modern-metadata-v0_l2fuf/django_contrib_comments-2.2.0.dist-info' Preparing metadata (pyproject.toml): finished with status 'done' Building wheels for collected packages: django-contrib-comments Building wheel for django-contrib-comments (pyproject.toml): started Running command Building wheel for django-contrib-comments (pyproject.toml) /usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) /usr/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running bdist_wheel running build running build_py creating build/lib/django_comments copying django_comments/moderation.py -> build/lib/django_comments copying django_comments/admin.py -> build/lib/django_comments copying django_comments/feeds.py -> build/lib/django_comments copying django_comments/compat.py -> build/lib/django_comments copying django_comments/signals.py -> build/lib/django_comments copying django_comments/apps.py -> build/lib/django_comments copying django_comments/urls.py -> build/lib/django_comments copying django_comments/abstracts.py -> build/lib/django_comments copying django_comments/__init__.py -> build/lib/django_comments copying django_comments/forms.py -> build/lib/django_comments copying django_comments/managers.py -> build/lib/django_comments copying django_comments/models.py -> build/lib/django_comments creating build/lib/django_comments/views copying django_comments/views/moderation.py -> build/lib/django_comments/views copying django_comments/views/comments.py -> build/lib/django_comments/views copying django_comments/views/__init__.py -> build/lib/django_comments/views copying django_comments/views/utils.py -> build/lib/django_comments/views creating build/lib/django_comments/management copying django_comments/management/__init__.py -> build/lib/django_comments/management creating build/lib/django_comments/templatetags copying django_comments/templatetags/comments.py -> build/lib/django_comments/templatetags copying django_comments/templatetags/__init__.py -> build/lib/django_comments/templatetags creating build/lib/django_comments/migrations copying django_comments/migrations/0001_initial.py -> build/lib/django_comments/migrations copying django_comments/migrations/0002_update_user_email_field_length.py -> build/lib/django_comments/migrations copying django_comments/migrations/0004_add_object_pk_is_removed_index.py -> build/lib/django_comments/migrations copying django_comments/migrations/__init__.py -> build/lib/django_comments/migrations copying django_comments/migrations/0003_add_submit_date_index.py -> build/lib/django_comments/migrations creating build/lib/django_comments/management/commands copying django_comments/management/commands/delete_stale_comments.py -> build/lib/django_comments/management/commands copying django_comments/management/commands/__init__.py -> build/lib/django_comments/management/commands running egg_info writing django_contrib_comments.egg-info/PKG-INFO writing dependency_links to django_contrib_comments.egg-info/dependency_links.txt writing requirements to django_contrib_comments.egg-info/requires.txt writing top-level names to django_contrib_comments.egg-info/top_level.txt reading manifest file 'django_contrib_comments.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files matching '__pycache__' found under directory '*' warning: no previously-included files matching '*.py[co]' found under directory '*' adding license file 'LICENSE.txt' writing manifest file 'django_contrib_comments.egg-info/SOURCES.txt' /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.af.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.af.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.af.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.af.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.af.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.ar.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.ar.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.ar.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.ar.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.ar.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.az.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.az.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.az.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.az.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.az.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.be.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.be.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.be.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.be.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.be.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.bg.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.bg.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.bg.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.bg.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.bg.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.bn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.bn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.bn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.bn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.bn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.br.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.br.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.br.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.br.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.br.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.bs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.bs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.bs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.bs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.bs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.ca.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.ca.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.ca.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.ca.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.ca.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.cs.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.cs.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.cs.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.cy.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.cy.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.cy.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.cy.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.cy.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.da.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.da.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.da.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.da.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.da.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.de.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.de.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.de.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.el.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.el.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.el.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.en.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.en.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.en.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.en_GB.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.en_GB.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.en_GB.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.en_GB.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.en_GB.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.eo.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.eo.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.eo.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.eo.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.eo.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.es.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.es.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.es.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.es_AR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.es_AR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.es_AR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.es_AR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.es_MX.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.es_MX.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.es_MX.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.es_MX.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.es_MX.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.et.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.et.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.et.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.et.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.et.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.eu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.eu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.eu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.eu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.eu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.fa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.fa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.fa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.fa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.fa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.fi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.fi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.fi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.fi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.fi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.fr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.fr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.fr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.fy_NL.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.fy_NL.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.fy_NL.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.fy_NL.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.fy_NL.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.ga.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.ga.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.ga.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.ga.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.ga.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.gd.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.gd.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.gd.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.gd.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.gd.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.gl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.gl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.gl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.gl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.gl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.he.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.he.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.he.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.he.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.he.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.hi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.hi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.hi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.hi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.hi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.hr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.hr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.hr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.hr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.hr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.hu.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.hu.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.hu.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.ia.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.ia.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.ia.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.ia.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.ia.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.id.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.id.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.id.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.id.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.id.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.is.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.is.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.is.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.is.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.is.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.it.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.it.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.it.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.ja.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.ja.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.ja.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.ja.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.ja.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.ka.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.ka.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.ka.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.ka.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.ka.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.kk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.kk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.kk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.kk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.kk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.km.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.km.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.km.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.km.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.km.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.kn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.kn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.kn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.kn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.kn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.ko.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.ko.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.ko.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.ko.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.ko.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.lt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.lt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.lt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.lv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.lv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.lv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.lv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.lv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.mk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.mk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.mk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.mk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.mk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.ml.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.ml.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.ml.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.ml.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.ml.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.mn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.mn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.mn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.mn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.mn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.nb.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.nb.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.nb.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.ne.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.ne.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.ne.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.ne.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.ne.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.nl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.nl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.nl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.nn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.nn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.nn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.nn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.nn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.pa.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.pa.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.pa.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.pa.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.pa.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.pl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.pl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.pl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.pt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.pt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.pt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.pt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.pt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.pt_BR.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.pt_BR.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.pt_BR.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.ro.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.ro.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.ro.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.ro.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.ro.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.ru.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.ru.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.ru.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.sk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.sk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.sk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.sk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.sk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.sl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.sl.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.sl.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.sl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.sl.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.sq.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.sq.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.sq.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.sq.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.sq.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.sr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.sr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.sr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.sr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.sr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.sr_Latn.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.sr_Latn.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.sr_Latn.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.sr_Latn.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.sr_Latn.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.sv.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.sv.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.sv.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.sw.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.sw.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.sw.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.sw.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.sw.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.ta.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.ta.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.ta.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.ta.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.ta.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.te.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.te.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.te.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.te.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.te.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.th.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.th.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.th.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.th.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.th.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.tr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.tr.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.tr.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.tr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.tr.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.tt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.tt.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.tt.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.tt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.tt.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.uk.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.uk.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.uk.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.ur.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.ur.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.ur.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.ur.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.ur.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.vi.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.vi.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.vi.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.vi.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.vi.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.zh_Hans.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.zh_Hans.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.zh_Hans.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.locale.zh_Hant.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.locale.zh_Hant.LC_MESSAGES' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.locale.zh_Hant.LC_MESSAGES' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.locale.zh_Hant.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_comments.locale.zh_Hant.LC_MESSAGES' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'django_comments.templates.comments' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_comments.templates.comments' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_comments.templates.comments' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_comments.templates.comments' to be distributed and are already explicitly excluding 'django_comments.templates.comments' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) creating build/lib/django_comments/locale/af/LC_MESSAGES copying django_comments/locale/af/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/af/LC_MESSAGES copying django_comments/locale/af/LC_MESSAGES/django.po -> build/lib/django_comments/locale/af/LC_MESSAGES creating build/lib/django_comments/locale/ar/LC_MESSAGES copying django_comments/locale/ar/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ar/LC_MESSAGES copying django_comments/locale/ar/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ar/LC_MESSAGES creating build/lib/django_comments/locale/az/LC_MESSAGES copying django_comments/locale/az/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/az/LC_MESSAGES copying django_comments/locale/az/LC_MESSAGES/django.po -> build/lib/django_comments/locale/az/LC_MESSAGES creating build/lib/django_comments/locale/be/LC_MESSAGES copying django_comments/locale/be/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/be/LC_MESSAGES copying django_comments/locale/be/LC_MESSAGES/django.po -> build/lib/django_comments/locale/be/LC_MESSAGES creating build/lib/django_comments/locale/bg/LC_MESSAGES copying django_comments/locale/bg/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/bg/LC_MESSAGES copying django_comments/locale/bg/LC_MESSAGES/django.po -> build/lib/django_comments/locale/bg/LC_MESSAGES creating build/lib/django_comments/locale/bn/LC_MESSAGES copying django_comments/locale/bn/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/bn/LC_MESSAGES copying django_comments/locale/bn/LC_MESSAGES/django.po -> build/lib/django_comments/locale/bn/LC_MESSAGES creating build/lib/django_comments/locale/br/LC_MESSAGES copying django_comments/locale/br/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/br/LC_MESSAGES copying django_comments/locale/br/LC_MESSAGES/django.po -> build/lib/django_comments/locale/br/LC_MESSAGES creating build/lib/django_comments/locale/bs/LC_MESSAGES copying django_comments/locale/bs/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/bs/LC_MESSAGES copying django_comments/locale/bs/LC_MESSAGES/django.po -> build/lib/django_comments/locale/bs/LC_MESSAGES creating build/lib/django_comments/locale/ca/LC_MESSAGES copying django_comments/locale/ca/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ca/LC_MESSAGES copying django_comments/locale/ca/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ca/LC_MESSAGES creating build/lib/django_comments/locale/cs/LC_MESSAGES copying django_comments/locale/cs/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/cs/LC_MESSAGES copying django_comments/locale/cs/LC_MESSAGES/django.po -> build/lib/django_comments/locale/cs/LC_MESSAGES creating build/lib/django_comments/locale/cy/LC_MESSAGES copying django_comments/locale/cy/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/cy/LC_MESSAGES copying django_comments/locale/cy/LC_MESSAGES/django.po -> build/lib/django_comments/locale/cy/LC_MESSAGES creating build/lib/django_comments/locale/da/LC_MESSAGES copying django_comments/locale/da/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/da/LC_MESSAGES copying django_comments/locale/da/LC_MESSAGES/django.po -> build/lib/django_comments/locale/da/LC_MESSAGES creating build/lib/django_comments/locale/de/LC_MESSAGES copying django_comments/locale/de/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/de/LC_MESSAGES copying django_comments/locale/de/LC_MESSAGES/django.po -> build/lib/django_comments/locale/de/LC_MESSAGES creating build/lib/django_comments/locale/el/LC_MESSAGES copying django_comments/locale/el/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/el/LC_MESSAGES copying django_comments/locale/el/LC_MESSAGES/django.po -> build/lib/django_comments/locale/el/LC_MESSAGES creating build/lib/django_comments/locale/en/LC_MESSAGES copying django_comments/locale/en/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/en/LC_MESSAGES copying django_comments/locale/en/LC_MESSAGES/django.po -> build/lib/django_comments/locale/en/LC_MESSAGES creating build/lib/django_comments/locale/en_GB/LC_MESSAGES copying django_comments/locale/en_GB/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/en_GB/LC_MESSAGES copying django_comments/locale/en_GB/LC_MESSAGES/django.po -> build/lib/django_comments/locale/en_GB/LC_MESSAGES creating build/lib/django_comments/locale/eo/LC_MESSAGES copying django_comments/locale/eo/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/eo/LC_MESSAGES copying django_comments/locale/eo/LC_MESSAGES/django.po -> build/lib/django_comments/locale/eo/LC_MESSAGES creating build/lib/django_comments/locale/es/LC_MESSAGES copying django_comments/locale/es/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/es/LC_MESSAGES copying django_comments/locale/es/LC_MESSAGES/django.po -> build/lib/django_comments/locale/es/LC_MESSAGES creating build/lib/django_comments/locale/es_AR/LC_MESSAGES copying django_comments/locale/es_AR/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/es_AR/LC_MESSAGES copying django_comments/locale/es_AR/LC_MESSAGES/django.po -> build/lib/django_comments/locale/es_AR/LC_MESSAGES creating build/lib/django_comments/locale/es_MX/LC_MESSAGES copying django_comments/locale/es_MX/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/es_MX/LC_MESSAGES copying django_comments/locale/es_MX/LC_MESSAGES/django.po -> build/lib/django_comments/locale/es_MX/LC_MESSAGES creating build/lib/django_comments/locale/et/LC_MESSAGES copying django_comments/locale/et/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/et/LC_MESSAGES copying django_comments/locale/et/LC_MESSAGES/django.po -> build/lib/django_comments/locale/et/LC_MESSAGES creating build/lib/django_comments/locale/eu/LC_MESSAGES copying django_comments/locale/eu/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/eu/LC_MESSAGES copying django_comments/locale/eu/LC_MESSAGES/django.po -> build/lib/django_comments/locale/eu/LC_MESSAGES creating build/lib/django_comments/locale/fa/LC_MESSAGES copying django_comments/locale/fa/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/fa/LC_MESSAGES copying django_comments/locale/fa/LC_MESSAGES/django.po -> build/lib/django_comments/locale/fa/LC_MESSAGES creating build/lib/django_comments/locale/fi/LC_MESSAGES copying django_comments/locale/fi/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/fi/LC_MESSAGES copying django_comments/locale/fi/LC_MESSAGES/django.po -> build/lib/django_comments/locale/fi/LC_MESSAGES creating build/lib/django_comments/locale/fr/LC_MESSAGES copying django_comments/locale/fr/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/fr/LC_MESSAGES copying django_comments/locale/fr/LC_MESSAGES/django.po -> build/lib/django_comments/locale/fr/LC_MESSAGES creating build/lib/django_comments/locale/fy_NL/LC_MESSAGES copying django_comments/locale/fy_NL/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/fy_NL/LC_MESSAGES copying django_comments/locale/fy_NL/LC_MESSAGES/django.po -> build/lib/django_comments/locale/fy_NL/LC_MESSAGES creating build/lib/django_comments/locale/ga/LC_MESSAGES copying django_comments/locale/ga/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ga/LC_MESSAGES copying django_comments/locale/ga/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ga/LC_MESSAGES creating build/lib/django_comments/locale/gd/LC_MESSAGES copying django_comments/locale/gd/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/gd/LC_MESSAGES copying django_comments/locale/gd/LC_MESSAGES/django.po -> build/lib/django_comments/locale/gd/LC_MESSAGES creating build/lib/django_comments/locale/gl/LC_MESSAGES copying django_comments/locale/gl/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/gl/LC_MESSAGES copying django_comments/locale/gl/LC_MESSAGES/django.po -> build/lib/django_comments/locale/gl/LC_MESSAGES creating build/lib/django_comments/locale/he/LC_MESSAGES copying django_comments/locale/he/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/he/LC_MESSAGES copying django_comments/locale/he/LC_MESSAGES/django.po -> build/lib/django_comments/locale/he/LC_MESSAGES creating build/lib/django_comments/locale/hi/LC_MESSAGES copying django_comments/locale/hi/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/hi/LC_MESSAGES copying django_comments/locale/hi/LC_MESSAGES/django.po -> build/lib/django_comments/locale/hi/LC_MESSAGES creating build/lib/django_comments/locale/hr/LC_MESSAGES copying django_comments/locale/hr/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/hr/LC_MESSAGES copying django_comments/locale/hr/LC_MESSAGES/django.po -> build/lib/django_comments/locale/hr/LC_MESSAGES creating build/lib/django_comments/locale/hu/LC_MESSAGES copying django_comments/locale/hu/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/hu/LC_MESSAGES copying django_comments/locale/hu/LC_MESSAGES/django.po -> build/lib/django_comments/locale/hu/LC_MESSAGES creating build/lib/django_comments/locale/ia/LC_MESSAGES copying django_comments/locale/ia/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ia/LC_MESSAGES copying django_comments/locale/ia/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ia/LC_MESSAGES creating build/lib/django_comments/locale/id/LC_MESSAGES copying django_comments/locale/id/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/id/LC_MESSAGES copying django_comments/locale/id/LC_MESSAGES/django.po -> build/lib/django_comments/locale/id/LC_MESSAGES creating build/lib/django_comments/locale/is/LC_MESSAGES copying django_comments/locale/is/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/is/LC_MESSAGES copying django_comments/locale/is/LC_MESSAGES/django.po -> build/lib/django_comments/locale/is/LC_MESSAGES creating build/lib/django_comments/locale/it/LC_MESSAGES copying django_comments/locale/it/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/it/LC_MESSAGES copying django_comments/locale/it/LC_MESSAGES/django.po -> build/lib/django_comments/locale/it/LC_MESSAGES creating build/lib/django_comments/locale/ja/LC_MESSAGES copying django_comments/locale/ja/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ja/LC_MESSAGES copying django_comments/locale/ja/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ja/LC_MESSAGES creating build/lib/django_comments/locale/ka/LC_MESSAGES copying django_comments/locale/ka/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ka/LC_MESSAGES copying django_comments/locale/ka/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ka/LC_MESSAGES creating build/lib/django_comments/locale/kk/LC_MESSAGES copying django_comments/locale/kk/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/kk/LC_MESSAGES copying django_comments/locale/kk/LC_MESSAGES/django.po -> build/lib/django_comments/locale/kk/LC_MESSAGES creating build/lib/django_comments/locale/km/LC_MESSAGES copying django_comments/locale/km/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/km/LC_MESSAGES copying django_comments/locale/km/LC_MESSAGES/django.po -> build/lib/django_comments/locale/km/LC_MESSAGES creating build/lib/django_comments/locale/kn/LC_MESSAGES copying django_comments/locale/kn/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/kn/LC_MESSAGES copying django_comments/locale/kn/LC_MESSAGES/django.po -> build/lib/django_comments/locale/kn/LC_MESSAGES creating build/lib/django_comments/locale/ko/LC_MESSAGES copying django_comments/locale/ko/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ko/LC_MESSAGES copying django_comments/locale/ko/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ko/LC_MESSAGES creating build/lib/django_comments/locale/lt/LC_MESSAGES copying django_comments/locale/lt/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/lt/LC_MESSAGES copying django_comments/locale/lt/LC_MESSAGES/django.po -> build/lib/django_comments/locale/lt/LC_MESSAGES creating build/lib/django_comments/locale/lv/LC_MESSAGES copying django_comments/locale/lv/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/lv/LC_MESSAGES copying django_comments/locale/lv/LC_MESSAGES/django.po -> build/lib/django_comments/locale/lv/LC_MESSAGES creating build/lib/django_comments/locale/mk/LC_MESSAGES copying django_comments/locale/mk/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/mk/LC_MESSAGES copying django_comments/locale/mk/LC_MESSAGES/django.po -> build/lib/django_comments/locale/mk/LC_MESSAGES creating build/lib/django_comments/locale/ml/LC_MESSAGES copying django_comments/locale/ml/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ml/LC_MESSAGES copying django_comments/locale/ml/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ml/LC_MESSAGES creating build/lib/django_comments/locale/mn/LC_MESSAGES copying django_comments/locale/mn/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/mn/LC_MESSAGES copying django_comments/locale/mn/LC_MESSAGES/django.po -> build/lib/django_comments/locale/mn/LC_MESSAGES creating build/lib/django_comments/locale/nb/LC_MESSAGES copying django_comments/locale/nb/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/nb/LC_MESSAGES copying django_comments/locale/nb/LC_MESSAGES/django.po -> build/lib/django_comments/locale/nb/LC_MESSAGES creating build/lib/django_comments/locale/ne/LC_MESSAGES copying django_comments/locale/ne/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ne/LC_MESSAGES copying django_comments/locale/ne/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ne/LC_MESSAGES creating build/lib/django_comments/locale/nl/LC_MESSAGES copying django_comments/locale/nl/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/nl/LC_MESSAGES copying django_comments/locale/nl/LC_MESSAGES/django.po -> build/lib/django_comments/locale/nl/LC_MESSAGES creating build/lib/django_comments/locale/nn/LC_MESSAGES copying django_comments/locale/nn/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/nn/LC_MESSAGES copying django_comments/locale/nn/LC_MESSAGES/django.po -> build/lib/django_comments/locale/nn/LC_MESSAGES creating build/lib/django_comments/locale/pa/LC_MESSAGES copying django_comments/locale/pa/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/pa/LC_MESSAGES copying django_comments/locale/pa/LC_MESSAGES/django.po -> build/lib/django_comments/locale/pa/LC_MESSAGES creating build/lib/django_comments/locale/pl/LC_MESSAGES copying django_comments/locale/pl/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/pl/LC_MESSAGES copying django_comments/locale/pl/LC_MESSAGES/django.po -> build/lib/django_comments/locale/pl/LC_MESSAGES creating build/lib/django_comments/locale/pt/LC_MESSAGES copying django_comments/locale/pt/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/pt/LC_MESSAGES copying django_comments/locale/pt/LC_MESSAGES/django.po -> build/lib/django_comments/locale/pt/LC_MESSAGES creating build/lib/django_comments/locale/pt_BR/LC_MESSAGES copying django_comments/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/pt_BR/LC_MESSAGES copying django_comments/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django_comments/locale/pt_BR/LC_MESSAGES creating build/lib/django_comments/locale/ro/LC_MESSAGES copying django_comments/locale/ro/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ro/LC_MESSAGES copying django_comments/locale/ro/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ro/LC_MESSAGES creating build/lib/django_comments/locale/ru/LC_MESSAGES copying django_comments/locale/ru/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ru/LC_MESSAGES copying django_comments/locale/ru/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ru/LC_MESSAGES creating build/lib/django_comments/locale/sk/LC_MESSAGES copying django_comments/locale/sk/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sk/LC_MESSAGES copying django_comments/locale/sk/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sk/LC_MESSAGES creating build/lib/django_comments/locale/sl/LC_MESSAGES copying django_comments/locale/sl/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sl/LC_MESSAGES copying django_comments/locale/sl/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sl/LC_MESSAGES creating build/lib/django_comments/locale/sq/LC_MESSAGES copying django_comments/locale/sq/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sq/LC_MESSAGES copying django_comments/locale/sq/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sq/LC_MESSAGES creating build/lib/django_comments/locale/sr/LC_MESSAGES copying django_comments/locale/sr/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sr/LC_MESSAGES copying django_comments/locale/sr/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sr/LC_MESSAGES creating build/lib/django_comments/locale/sr_Latn/LC_MESSAGES copying django_comments/locale/sr_Latn/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sr_Latn/LC_MESSAGES copying django_comments/locale/sr_Latn/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sr_Latn/LC_MESSAGES creating build/lib/django_comments/locale/sv/LC_MESSAGES copying django_comments/locale/sv/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sv/LC_MESSAGES copying django_comments/locale/sv/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sv/LC_MESSAGES creating build/lib/django_comments/locale/sw/LC_MESSAGES copying django_comments/locale/sw/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/sw/LC_MESSAGES copying django_comments/locale/sw/LC_MESSAGES/django.po -> build/lib/django_comments/locale/sw/LC_MESSAGES creating build/lib/django_comments/locale/ta/LC_MESSAGES copying django_comments/locale/ta/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ta/LC_MESSAGES copying django_comments/locale/ta/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ta/LC_MESSAGES creating build/lib/django_comments/locale/te/LC_MESSAGES copying django_comments/locale/te/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/te/LC_MESSAGES copying django_comments/locale/te/LC_MESSAGES/django.po -> build/lib/django_comments/locale/te/LC_MESSAGES creating build/lib/django_comments/locale/th/LC_MESSAGES copying django_comments/locale/th/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/th/LC_MESSAGES copying django_comments/locale/th/LC_MESSAGES/django.po -> build/lib/django_comments/locale/th/LC_MESSAGES creating build/lib/django_comments/locale/tr/LC_MESSAGES copying django_comments/locale/tr/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/tr/LC_MESSAGES copying django_comments/locale/tr/LC_MESSAGES/django.po -> build/lib/django_comments/locale/tr/LC_MESSAGES creating build/lib/django_comments/locale/tt/LC_MESSAGES copying django_comments/locale/tt/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/tt/LC_MESSAGES copying django_comments/locale/tt/LC_MESSAGES/django.po -> build/lib/django_comments/locale/tt/LC_MESSAGES creating build/lib/django_comments/locale/uk/LC_MESSAGES copying django_comments/locale/uk/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/uk/LC_MESSAGES copying django_comments/locale/uk/LC_MESSAGES/django.po -> build/lib/django_comments/locale/uk/LC_MESSAGES creating build/lib/django_comments/locale/ur/LC_MESSAGES copying django_comments/locale/ur/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/ur/LC_MESSAGES copying django_comments/locale/ur/LC_MESSAGES/django.po -> build/lib/django_comments/locale/ur/LC_MESSAGES creating build/lib/django_comments/locale/vi/LC_MESSAGES copying django_comments/locale/vi/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/vi/LC_MESSAGES copying django_comments/locale/vi/LC_MESSAGES/django.po -> build/lib/django_comments/locale/vi/LC_MESSAGES creating build/lib/django_comments/locale/zh_Hans/LC_MESSAGES copying django_comments/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/zh_Hans/LC_MESSAGES copying django_comments/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django_comments/locale/zh_Hans/LC_MESSAGES creating build/lib/django_comments/locale/zh_Hant/LC_MESSAGES copying django_comments/locale/zh_Hant/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/zh_Hant/LC_MESSAGES copying django_comments/locale/zh_Hant/LC_MESSAGES/django.po -> build/lib/django_comments/locale/zh_Hant/LC_MESSAGES creating build/lib/django_comments/templates/comments copying django_comments/templates/comments/400-debug.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/approve.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/approved.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/base.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/delete.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/deleted.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/flag.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/flagged.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/form.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/list.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/posted.html -> build/lib/django_comments/templates/comments copying django_comments/templates/comments/preview.html -> build/lib/django_comments/templates/comments installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/django_comments copying build/lib/django_comments/moderation.py -> build/bdist.linux-x86_64/wheel/./django_comments copying build/lib/django_comments/admin.py -> build/bdist.linux-x86_64/wheel/./django_comments copying build/lib/django_comments/feeds.py -> build/bdist.linux-x86_64/wheel/./django_comments creating build/bdist.linux-x86_64/wheel/django_comments/views copying build/lib/django_comments/views/moderation.py -> build/bdist.linux-x86_64/wheel/./django_comments/views copying build/lib/django_comments/views/comments.py -> build/bdist.linux-x86_64/wheel/./django_comments/views copying build/lib/django_comments/views/__init__.py -> build/bdist.linux-x86_64/wheel/./django_comments/views copying build/lib/django_comments/views/utils.py -> build/bdist.linux-x86_64/wheel/./django_comments/views creating build/bdist.linux-x86_64/wheel/django_comments/management creating build/bdist.linux-x86_64/wheel/django_comments/management/commands copying build/lib/django_comments/management/commands/delete_stale_comments.py -> build/bdist.linux-x86_64/wheel/./django_comments/management/commands copying build/lib/django_comments/management/commands/__init__.py -> build/bdist.linux-x86_64/wheel/./django_comments/management/commands copying build/lib/django_comments/management/__init__.py -> build/bdist.linux-x86_64/wheel/./django_comments/management creating build/bdist.linux-x86_64/wheel/django_comments/templates creating build/bdist.linux-x86_64/wheel/django_comments/templates/comments copying build/lib/django_comments/templates/comments/preview.html -> build/bdist.linux-x86_64/wheel/./django_comments/templates/comments copying build/lib/django_comments/templates/comments/form.html -> build/bdist.linux-x86_64/wheel/./django_comments/templates/comments copying build/lib/django_comments/templates/comments/400-debug.html -> build/bdist.linux-x86_64/wheel/./django_comments/templates/comments copying build/lib/django_comments/templates/comments/approve.html -> build/bdist.linux-x86_64/wheel/./django_comments/templates/comments copying build/lib/django_comments/templates/comments/list.html -> build/bdist.linux-x86_64/wheel/./django_comments/templates/comments copying build/lib/django_comments/templates/comments/flagged.html -> build/bdist.linux-x86_64/wheel/./django_comments/templates/comments copying build/lib/django_comments/templates/comments/deleted.html -> build/bdist.linux-x86_64/wheel/./django_comments/templates/comments copying build/lib/django_comments/templates/comments/flag.html -> build/bdist.linux-x86_64/wheel/./django_comments/templates/comments copying build/lib/django_comments/templates/comments/delete.html -> build/bdist.linux-x86_64/wheel/./django_comments/templates/comments copying build/lib/django_comments/templates/comments/base.html -> build/bdist.linux-x86_64/wheel/./django_comments/templates/comments copying build/lib/django_comments/templates/comments/approved.html -> build/bdist.linux-x86_64/wheel/./django_comments/templates/comments copying build/lib/django_comments/templates/comments/posted.html -> build/bdist.linux-x86_64/wheel/./django_comments/templates/comments copying build/lib/django_comments/compat.py -> build/bdist.linux-x86_64/wheel/./django_comments copying build/lib/django_comments/signals.py -> build/bdist.linux-x86_64/wheel/./django_comments creating build/bdist.linux-x86_64/wheel/django_comments/locale creating build/bdist.linux-x86_64/wheel/django_comments/locale/hi creating build/bdist.linux-x86_64/wheel/django_comments/locale/hi/LC_MESSAGES copying build/lib/django_comments/locale/hi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/hi/LC_MESSAGES copying build/lib/django_comments/locale/hi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/hi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/pt creating build/bdist.linux-x86_64/wheel/django_comments/locale/pt/LC_MESSAGES copying build/lib/django_comments/locale/pt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/pt/LC_MESSAGES copying build/lib/django_comments/locale/pt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/pt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/lv creating build/bdist.linux-x86_64/wheel/django_comments/locale/lv/LC_MESSAGES copying build/lib/django_comments/locale/lv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/lv/LC_MESSAGES copying build/lib/django_comments/locale/lv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/lv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/en_GB creating build/bdist.linux-x86_64/wheel/django_comments/locale/en_GB/LC_MESSAGES copying build/lib/django_comments/locale/en_GB/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/en_GB/LC_MESSAGES copying build/lib/django_comments/locale/en_GB/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/en_GB/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/ca creating build/bdist.linux-x86_64/wheel/django_comments/locale/ca/LC_MESSAGES copying build/lib/django_comments/locale/ca/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ca/LC_MESSAGES copying build/lib/django_comments/locale/ca/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ca/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/sq creating build/bdist.linux-x86_64/wheel/django_comments/locale/sq/LC_MESSAGES copying build/lib/django_comments/locale/sq/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sq/LC_MESSAGES copying build/lib/django_comments/locale/sq/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sq/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/nb creating build/bdist.linux-x86_64/wheel/django_comments/locale/nb/LC_MESSAGES copying build/lib/django_comments/locale/nb/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/nb/LC_MESSAGES copying build/lib/django_comments/locale/nb/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/nb/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/sv creating build/bdist.linux-x86_64/wheel/django_comments/locale/sv/LC_MESSAGES copying build/lib/django_comments/locale/sv/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sv/LC_MESSAGES copying build/lib/django_comments/locale/sv/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sv/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/tr creating build/bdist.linux-x86_64/wheel/django_comments/locale/tr/LC_MESSAGES copying build/lib/django_comments/locale/tr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/tr/LC_MESSAGES copying build/lib/django_comments/locale/tr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/tr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/hr creating build/bdist.linux-x86_64/wheel/django_comments/locale/hr/LC_MESSAGES copying build/lib/django_comments/locale/hr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/hr/LC_MESSAGES copying build/lib/django_comments/locale/hr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/hr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/mk creating build/bdist.linux-x86_64/wheel/django_comments/locale/mk/LC_MESSAGES copying build/lib/django_comments/locale/mk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/mk/LC_MESSAGES copying build/lib/django_comments/locale/mk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/mk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/sl creating build/bdist.linux-x86_64/wheel/django_comments/locale/sl/LC_MESSAGES copying build/lib/django_comments/locale/sl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sl/LC_MESSAGES copying build/lib/django_comments/locale/sl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/en creating build/bdist.linux-x86_64/wheel/django_comments/locale/en/LC_MESSAGES copying build/lib/django_comments/locale/en/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/en/LC_MESSAGES copying build/lib/django_comments/locale/en/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/en/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/es creating build/bdist.linux-x86_64/wheel/django_comments/locale/es/LC_MESSAGES copying build/lib/django_comments/locale/es/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/es/LC_MESSAGES copying build/lib/django_comments/locale/es/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/es/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/ne creating build/bdist.linux-x86_64/wheel/django_comments/locale/ne/LC_MESSAGES copying build/lib/django_comments/locale/ne/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ne/LC_MESSAGES copying build/lib/django_comments/locale/ne/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ne/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/kk creating build/bdist.linux-x86_64/wheel/django_comments/locale/kk/LC_MESSAGES copying build/lib/django_comments/locale/kk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/kk/LC_MESSAGES copying build/lib/django_comments/locale/kk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/kk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/br creating build/bdist.linux-x86_64/wheel/django_comments/locale/br/LC_MESSAGES copying build/lib/django_comments/locale/br/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/br/LC_MESSAGES copying build/lib/django_comments/locale/br/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/br/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/nn creating build/bdist.linux-x86_64/wheel/django_comments/locale/nn/LC_MESSAGES copying build/lib/django_comments/locale/nn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/nn/LC_MESSAGES copying build/lib/django_comments/locale/nn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/nn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/ar creating build/bdist.linux-x86_64/wheel/django_comments/locale/ar/LC_MESSAGES copying build/lib/django_comments/locale/ar/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ar/LC_MESSAGES copying build/lib/django_comments/locale/ar/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ar/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/bs creating build/bdist.linux-x86_64/wheel/django_comments/locale/bs/LC_MESSAGES copying build/lib/django_comments/locale/bs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/bs/LC_MESSAGES copying build/lib/django_comments/locale/bs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/bs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/fa creating build/bdist.linux-x86_64/wheel/django_comments/locale/fa/LC_MESSAGES copying build/lib/django_comments/locale/fa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/fa/LC_MESSAGES copying build/lib/django_comments/locale/fa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/fa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/km creating build/bdist.linux-x86_64/wheel/django_comments/locale/km/LC_MESSAGES copying build/lib/django_comments/locale/km/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/km/LC_MESSAGES copying build/lib/django_comments/locale/km/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/km/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/ia creating build/bdist.linux-x86_64/wheel/django_comments/locale/ia/LC_MESSAGES copying build/lib/django_comments/locale/ia/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ia/LC_MESSAGES copying build/lib/django_comments/locale/ia/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ia/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/ro creating build/bdist.linux-x86_64/wheel/django_comments/locale/ro/LC_MESSAGES copying build/lib/django_comments/locale/ro/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ro/LC_MESSAGES copying build/lib/django_comments/locale/ro/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ro/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/tt creating build/bdist.linux-x86_64/wheel/django_comments/locale/tt/LC_MESSAGES copying build/lib/django_comments/locale/tt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/tt/LC_MESSAGES copying build/lib/django_comments/locale/tt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/tt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/ru creating build/bdist.linux-x86_64/wheel/django_comments/locale/ru/LC_MESSAGES copying build/lib/django_comments/locale/ru/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ru/LC_MESSAGES copying build/lib/django_comments/locale/ru/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ru/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/sw creating build/bdist.linux-x86_64/wheel/django_comments/locale/sw/LC_MESSAGES copying build/lib/django_comments/locale/sw/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sw/LC_MESSAGES copying build/lib/django_comments/locale/sw/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sw/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/da creating build/bdist.linux-x86_64/wheel/django_comments/locale/da/LC_MESSAGES copying build/lib/django_comments/locale/da/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/da/LC_MESSAGES copying build/lib/django_comments/locale/da/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/da/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/hu creating build/bdist.linux-x86_64/wheel/django_comments/locale/hu/LC_MESSAGES copying build/lib/django_comments/locale/hu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/hu/LC_MESSAGES copying build/lib/django_comments/locale/hu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/hu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/az creating build/bdist.linux-x86_64/wheel/django_comments/locale/az/LC_MESSAGES copying build/lib/django_comments/locale/az/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/az/LC_MESSAGES copying build/lib/django_comments/locale/az/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/az/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/fr creating build/bdist.linux-x86_64/wheel/django_comments/locale/fr/LC_MESSAGES copying build/lib/django_comments/locale/fr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/fr/LC_MESSAGES copying build/lib/django_comments/locale/fr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/fr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/kn creating build/bdist.linux-x86_64/wheel/django_comments/locale/kn/LC_MESSAGES copying build/lib/django_comments/locale/kn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/kn/LC_MESSAGES copying build/lib/django_comments/locale/kn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/kn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/ga creating build/bdist.linux-x86_64/wheel/django_comments/locale/ga/LC_MESSAGES copying build/lib/django_comments/locale/ga/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ga/LC_MESSAGES copying build/lib/django_comments/locale/ga/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ga/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/ta creating build/bdist.linux-x86_64/wheel/django_comments/locale/ta/LC_MESSAGES copying build/lib/django_comments/locale/ta/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ta/LC_MESSAGES copying build/lib/django_comments/locale/ta/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ta/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/sr creating build/bdist.linux-x86_64/wheel/django_comments/locale/sr/LC_MESSAGES copying build/lib/django_comments/locale/sr/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sr/LC_MESSAGES copying build/lib/django_comments/locale/sr/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sr/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/th creating build/bdist.linux-x86_64/wheel/django_comments/locale/th/LC_MESSAGES copying build/lib/django_comments/locale/th/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/th/LC_MESSAGES copying build/lib/django_comments/locale/th/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/th/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/gl creating build/bdist.linux-x86_64/wheel/django_comments/locale/gl/LC_MESSAGES copying build/lib/django_comments/locale/gl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/gl/LC_MESSAGES copying build/lib/django_comments/locale/gl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/gl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/be creating build/bdist.linux-x86_64/wheel/django_comments/locale/be/LC_MESSAGES copying build/lib/django_comments/locale/be/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/be/LC_MESSAGES copying build/lib/django_comments/locale/be/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/be/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/cy creating build/bdist.linux-x86_64/wheel/django_comments/locale/cy/LC_MESSAGES copying build/lib/django_comments/locale/cy/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/cy/LC_MESSAGES copying build/lib/django_comments/locale/cy/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/cy/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/ka creating build/bdist.linux-x86_64/wheel/django_comments/locale/ka/LC_MESSAGES copying build/lib/django_comments/locale/ka/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ka/LC_MESSAGES copying build/lib/django_comments/locale/ka/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ka/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/id creating build/bdist.linux-x86_64/wheel/django_comments/locale/id/LC_MESSAGES copying build/lib/django_comments/locale/id/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/id/LC_MESSAGES copying build/lib/django_comments/locale/id/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/id/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/mn creating build/bdist.linux-x86_64/wheel/django_comments/locale/mn/LC_MESSAGES copying build/lib/django_comments/locale/mn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/mn/LC_MESSAGES copying build/lib/django_comments/locale/mn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/mn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/nl creating build/bdist.linux-x86_64/wheel/django_comments/locale/nl/LC_MESSAGES copying build/lib/django_comments/locale/nl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/nl/LC_MESSAGES copying build/lib/django_comments/locale/nl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/nl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/sk creating build/bdist.linux-x86_64/wheel/django_comments/locale/sk/LC_MESSAGES copying build/lib/django_comments/locale/sk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sk/LC_MESSAGES copying build/lib/django_comments/locale/sk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/ml creating build/bdist.linux-x86_64/wheel/django_comments/locale/ml/LC_MESSAGES copying build/lib/django_comments/locale/ml/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ml/LC_MESSAGES copying build/lib/django_comments/locale/ml/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ml/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/ko creating build/bdist.linux-x86_64/wheel/django_comments/locale/ko/LC_MESSAGES copying build/lib/django_comments/locale/ko/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ko/LC_MESSAGES copying build/lib/django_comments/locale/ko/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ko/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/gd creating build/bdist.linux-x86_64/wheel/django_comments/locale/gd/LC_MESSAGES copying build/lib/django_comments/locale/gd/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/gd/LC_MESSAGES copying build/lib/django_comments/locale/gd/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/gd/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/he creating build/bdist.linux-x86_64/wheel/django_comments/locale/he/LC_MESSAGES copying build/lib/django_comments/locale/he/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/he/LC_MESSAGES copying build/lib/django_comments/locale/he/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/he/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/vi creating build/bdist.linux-x86_64/wheel/django_comments/locale/vi/LC_MESSAGES copying build/lib/django_comments/locale/vi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/vi/LC_MESSAGES copying build/lib/django_comments/locale/vi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/vi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/ja creating build/bdist.linux-x86_64/wheel/django_comments/locale/ja/LC_MESSAGES copying build/lib/django_comments/locale/ja/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ja/LC_MESSAGES copying build/lib/django_comments/locale/ja/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ja/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/es_AR creating build/bdist.linux-x86_64/wheel/django_comments/locale/es_AR/LC_MESSAGES copying build/lib/django_comments/locale/es_AR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/es_AR/LC_MESSAGES copying build/lib/django_comments/locale/es_AR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/es_AR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/is creating build/bdist.linux-x86_64/wheel/django_comments/locale/is/LC_MESSAGES copying build/lib/django_comments/locale/is/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/is/LC_MESSAGES copying build/lib/django_comments/locale/is/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/is/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/ur creating build/bdist.linux-x86_64/wheel/django_comments/locale/ur/LC_MESSAGES copying build/lib/django_comments/locale/ur/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ur/LC_MESSAGES copying build/lib/django_comments/locale/ur/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/ur/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/et creating build/bdist.linux-x86_64/wheel/django_comments/locale/et/LC_MESSAGES copying build/lib/django_comments/locale/et/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/et/LC_MESSAGES copying build/lib/django_comments/locale/et/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/et/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/pl creating build/bdist.linux-x86_64/wheel/django_comments/locale/pl/LC_MESSAGES copying build/lib/django_comments/locale/pl/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/pl/LC_MESSAGES copying build/lib/django_comments/locale/pl/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/pl/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/sr_Latn creating build/bdist.linux-x86_64/wheel/django_comments/locale/sr_Latn/LC_MESSAGES copying build/lib/django_comments/locale/sr_Latn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sr_Latn/LC_MESSAGES copying build/lib/django_comments/locale/sr_Latn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/sr_Latn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/fy_NL creating build/bdist.linux-x86_64/wheel/django_comments/locale/fy_NL/LC_MESSAGES copying build/lib/django_comments/locale/fy_NL/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/fy_NL/LC_MESSAGES copying build/lib/django_comments/locale/fy_NL/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/fy_NL/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/uk creating build/bdist.linux-x86_64/wheel/django_comments/locale/uk/LC_MESSAGES copying build/lib/django_comments/locale/uk/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/uk/LC_MESSAGES copying build/lib/django_comments/locale/uk/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/uk/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/el creating build/bdist.linux-x86_64/wheel/django_comments/locale/el/LC_MESSAGES copying build/lib/django_comments/locale/el/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/el/LC_MESSAGES copying build/lib/django_comments/locale/el/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/el/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/de creating build/bdist.linux-x86_64/wheel/django_comments/locale/de/LC_MESSAGES copying build/lib/django_comments/locale/de/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/de/LC_MESSAGES copying build/lib/django_comments/locale/de/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/de/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/bn creating build/bdist.linux-x86_64/wheel/django_comments/locale/bn/LC_MESSAGES copying build/lib/django_comments/locale/bn/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/bn/LC_MESSAGES copying build/lib/django_comments/locale/bn/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/bn/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/bg creating build/bdist.linux-x86_64/wheel/django_comments/locale/bg/LC_MESSAGES copying build/lib/django_comments/locale/bg/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/bg/LC_MESSAGES copying build/lib/django_comments/locale/bg/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/bg/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/pa creating build/bdist.linux-x86_64/wheel/django_comments/locale/pa/LC_MESSAGES copying build/lib/django_comments/locale/pa/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/pa/LC_MESSAGES copying build/lib/django_comments/locale/pa/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/pa/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/af creating build/bdist.linux-x86_64/wheel/django_comments/locale/af/LC_MESSAGES copying build/lib/django_comments/locale/af/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/af/LC_MESSAGES copying build/lib/django_comments/locale/af/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/af/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/zh_Hant creating build/bdist.linux-x86_64/wheel/django_comments/locale/zh_Hant/LC_MESSAGES copying build/lib/django_comments/locale/zh_Hant/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/zh_Hant/LC_MESSAGES copying build/lib/django_comments/locale/zh_Hant/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/zh_Hant/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/eu creating build/bdist.linux-x86_64/wheel/django_comments/locale/eu/LC_MESSAGES copying build/lib/django_comments/locale/eu/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/eu/LC_MESSAGES copying build/lib/django_comments/locale/eu/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/eu/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/it creating build/bdist.linux-x86_64/wheel/django_comments/locale/it/LC_MESSAGES copying build/lib/django_comments/locale/it/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/it/LC_MESSAGES copying build/lib/django_comments/locale/it/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/it/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/pt_BR creating build/bdist.linux-x86_64/wheel/django_comments/locale/pt_BR/LC_MESSAGES copying build/lib/django_comments/locale/pt_BR/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/pt_BR/LC_MESSAGES copying build/lib/django_comments/locale/pt_BR/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/pt_BR/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/lt creating build/bdist.linux-x86_64/wheel/django_comments/locale/lt/LC_MESSAGES copying build/lib/django_comments/locale/lt/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/lt/LC_MESSAGES copying build/lib/django_comments/locale/lt/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/lt/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/eo creating build/bdist.linux-x86_64/wheel/django_comments/locale/eo/LC_MESSAGES copying build/lib/django_comments/locale/eo/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/eo/LC_MESSAGES copying build/lib/django_comments/locale/eo/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/eo/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/cs creating build/bdist.linux-x86_64/wheel/django_comments/locale/cs/LC_MESSAGES copying build/lib/django_comments/locale/cs/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/cs/LC_MESSAGES copying build/lib/django_comments/locale/cs/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/cs/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/te creating build/bdist.linux-x86_64/wheel/django_comments/locale/te/LC_MESSAGES copying build/lib/django_comments/locale/te/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/te/LC_MESSAGES copying build/lib/django_comments/locale/te/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/te/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/fi creating build/bdist.linux-x86_64/wheel/django_comments/locale/fi/LC_MESSAGES copying build/lib/django_comments/locale/fi/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/fi/LC_MESSAGES copying build/lib/django_comments/locale/fi/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/fi/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/es_MX creating build/bdist.linux-x86_64/wheel/django_comments/locale/es_MX/LC_MESSAGES copying build/lib/django_comments/locale/es_MX/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/es_MX/LC_MESSAGES copying build/lib/django_comments/locale/es_MX/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/es_MX/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/locale/zh_Hans creating build/bdist.linux-x86_64/wheel/django_comments/locale/zh_Hans/LC_MESSAGES copying build/lib/django_comments/locale/zh_Hans/LC_MESSAGES/django.po -> build/bdist.linux-x86_64/wheel/./django_comments/locale/zh_Hans/LC_MESSAGES copying build/lib/django_comments/locale/zh_Hans/LC_MESSAGES/django.mo -> build/bdist.linux-x86_64/wheel/./django_comments/locale/zh_Hans/LC_MESSAGES creating build/bdist.linux-x86_64/wheel/django_comments/templatetags copying build/lib/django_comments/templatetags/comments.py -> build/bdist.linux-x86_64/wheel/./django_comments/templatetags copying build/lib/django_comments/templatetags/__init__.py -> build/bdist.linux-x86_64/wheel/./django_comments/templatetags copying build/lib/django_comments/apps.py -> build/bdist.linux-x86_64/wheel/./django_comments copying build/lib/django_comments/urls.py -> build/bdist.linux-x86_64/wheel/./django_comments copying build/lib/django_comments/abstracts.py -> build/bdist.linux-x86_64/wheel/./django_comments copying build/lib/django_comments/__init__.py -> build/bdist.linux-x86_64/wheel/./django_comments creating build/bdist.linux-x86_64/wheel/django_comments/migrations copying build/lib/django_comments/migrations/0001_initial.py -> build/bdist.linux-x86_64/wheel/./django_comments/migrations copying build/lib/django_comments/migrations/0002_update_user_email_field_length.py -> build/bdist.linux-x86_64/wheel/./django_comments/migrations copying build/lib/django_comments/migrations/0004_add_object_pk_is_removed_index.py -> build/bdist.linux-x86_64/wheel/./django_comments/migrations copying build/lib/django_comments/migrations/__init__.py -> build/bdist.linux-x86_64/wheel/./django_comments/migrations copying build/lib/django_comments/migrations/0003_add_submit_date_index.py -> build/bdist.linux-x86_64/wheel/./django_comments/migrations copying build/lib/django_comments/forms.py -> build/bdist.linux-x86_64/wheel/./django_comments copying build/lib/django_comments/managers.py -> build/bdist.linux-x86_64/wheel/./django_comments copying build/lib/django_comments/models.py -> build/bdist.linux-x86_64/wheel/./django_comments running install_egg_info Copying django_contrib_comments.egg-info to build/bdist.linux-x86_64/wheel/./django_contrib_comments-2.2.0-py3.13.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/django_contrib_comments-2.2.0.dist-info/WHEEL creating '/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir/pip-wheel-cc7vot9b/.tmp-j9m4p0sz/django_contrib_comments-2.2.0-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'django_comments/__init__.py' adding 'django_comments/abstracts.py' adding 'django_comments/admin.py' adding 'django_comments/apps.py' adding 'django_comments/compat.py' adding 'django_comments/feeds.py' adding 'django_comments/forms.py' adding 'django_comments/managers.py' adding 'django_comments/models.py' adding 'django_comments/moderation.py' adding 'django_comments/signals.py' adding 'django_comments/urls.py' adding 'django_comments/locale/af/LC_MESSAGES/django.mo' adding 'django_comments/locale/af/LC_MESSAGES/django.po' adding 'django_comments/locale/ar/LC_MESSAGES/django.mo' adding 'django_comments/locale/ar/LC_MESSAGES/django.po' adding 'django_comments/locale/az/LC_MESSAGES/django.mo' adding 'django_comments/locale/az/LC_MESSAGES/django.po' adding 'django_comments/locale/be/LC_MESSAGES/django.mo' adding 'django_comments/locale/be/LC_MESSAGES/django.po' adding 'django_comments/locale/bg/LC_MESSAGES/django.mo' adding 'django_comments/locale/bg/LC_MESSAGES/django.po' adding 'django_comments/locale/bn/LC_MESSAGES/django.mo' adding 'django_comments/locale/bn/LC_MESSAGES/django.po' adding 'django_comments/locale/br/LC_MESSAGES/django.mo' adding 'django_comments/locale/br/LC_MESSAGES/django.po' adding 'django_comments/locale/bs/LC_MESSAGES/django.mo' adding 'django_comments/locale/bs/LC_MESSAGES/django.po' adding 'django_comments/locale/ca/LC_MESSAGES/django.mo' adding 'django_comments/locale/ca/LC_MESSAGES/django.po' adding 'django_comments/locale/cs/LC_MESSAGES/django.mo' adding 'django_comments/locale/cs/LC_MESSAGES/django.po' adding 'django_comments/locale/cy/LC_MESSAGES/django.mo' adding 'django_comments/locale/cy/LC_MESSAGES/django.po' adding 'django_comments/locale/da/LC_MESSAGES/django.mo' adding 'django_comments/locale/da/LC_MESSAGES/django.po' adding 'django_comments/locale/de/LC_MESSAGES/django.mo' adding 'django_comments/locale/de/LC_MESSAGES/django.po' adding 'django_comments/locale/el/LC_MESSAGES/django.mo' adding 'django_comments/locale/el/LC_MESSAGES/django.po' adding 'django_comments/locale/en/LC_MESSAGES/django.mo' adding 'django_comments/locale/en/LC_MESSAGES/django.po' adding 'django_comments/locale/en_GB/LC_MESSAGES/django.mo' adding 'django_comments/locale/en_GB/LC_MESSAGES/django.po' adding 'django_comments/locale/eo/LC_MESSAGES/django.mo' adding 'django_comments/locale/eo/LC_MESSAGES/django.po' adding 'django_comments/locale/es/LC_MESSAGES/django.mo' adding 'django_comments/locale/es/LC_MESSAGES/django.po' adding 'django_comments/locale/es_AR/LC_MESSAGES/django.mo' adding 'django_comments/locale/es_AR/LC_MESSAGES/django.po' adding 'django_comments/locale/es_MX/LC_MESSAGES/django.mo' adding 'django_comments/locale/es_MX/LC_MESSAGES/django.po' adding 'django_comments/locale/et/LC_MESSAGES/django.mo' adding 'django_comments/locale/et/LC_MESSAGES/django.po' adding 'django_comments/locale/eu/LC_MESSAGES/django.mo' adding 'django_comments/locale/eu/LC_MESSAGES/django.po' adding 'django_comments/locale/fa/LC_MESSAGES/django.mo' adding 'django_comments/locale/fa/LC_MESSAGES/django.po' adding 'django_comments/locale/fi/LC_MESSAGES/django.mo' adding 'django_comments/locale/fi/LC_MESSAGES/django.po' adding 'django_comments/locale/fr/LC_MESSAGES/django.mo' adding 'django_comments/locale/fr/LC_MESSAGES/django.po' adding 'django_comments/locale/fy_NL/LC_MESSAGES/django.mo' adding 'django_comments/locale/fy_NL/LC_MESSAGES/django.po' adding 'django_comments/locale/ga/LC_MESSAGES/django.mo' adding 'django_comments/locale/ga/LC_MESSAGES/django.po' adding 'django_comments/locale/gd/LC_MESSAGES/django.mo' adding 'django_comments/locale/gd/LC_MESSAGES/django.po' adding 'django_comments/locale/gl/LC_MESSAGES/django.mo' adding 'django_comments/locale/gl/LC_MESSAGES/django.po' adding 'django_comments/locale/he/LC_MESSAGES/django.mo' adding 'django_comments/locale/he/LC_MESSAGES/django.po' adding 'django_comments/locale/hi/LC_MESSAGES/django.mo' adding 'django_comments/locale/hi/LC_MESSAGES/django.po' adding 'django_comments/locale/hr/LC_MESSAGES/django.mo' adding 'django_comments/locale/hr/LC_MESSAGES/django.po' adding 'django_comments/locale/hu/LC_MESSAGES/django.mo' adding 'django_comments/locale/hu/LC_MESSAGES/django.po' adding 'django_comments/locale/ia/LC_MESSAGES/django.mo' adding 'django_comments/locale/ia/LC_MESSAGES/django.po' adding 'django_comments/locale/id/LC_MESSAGES/django.mo' adding 'django_comments/locale/id/LC_MESSAGES/django.po' adding 'django_comments/locale/is/LC_MESSAGES/django.mo' adding 'django_comments/locale/is/LC_MESSAGES/django.po' adding 'django_comments/locale/it/LC_MESSAGES/django.mo' adding 'django_comments/locale/it/LC_MESSAGES/django.po' adding 'django_comments/locale/ja/LC_MESSAGES/django.mo' adding 'django_comments/locale/ja/LC_MESSAGES/django.po' adding 'django_comments/locale/ka/LC_MESSAGES/django.mo' adding 'django_comments/locale/ka/LC_MESSAGES/django.po' adding 'django_comments/locale/kk/LC_MESSAGES/django.mo' adding 'django_comments/locale/kk/LC_MESSAGES/django.po' adding 'django_comments/locale/km/LC_MESSAGES/django.mo' adding 'django_comments/locale/km/LC_MESSAGES/django.po' adding 'django_comments/locale/kn/LC_MESSAGES/django.mo' adding 'django_comments/locale/kn/LC_MESSAGES/django.po' adding 'django_comments/locale/ko/LC_MESSAGES/django.mo' adding 'django_comments/locale/ko/LC_MESSAGES/django.po' adding 'django_comments/locale/lt/LC_MESSAGES/django.mo' adding 'django_comments/locale/lt/LC_MESSAGES/django.po' adding 'django_comments/locale/lv/LC_MESSAGES/django.mo' adding 'django_comments/locale/lv/LC_MESSAGES/django.po' adding 'django_comments/locale/mk/LC_MESSAGES/django.mo' adding 'django_comments/locale/mk/LC_MESSAGES/django.po' adding 'django_comments/locale/ml/LC_MESSAGES/django.mo' adding 'django_comments/locale/ml/LC_MESSAGES/django.po' adding 'django_comments/locale/mn/LC_MESSAGES/django.mo' adding 'django_comments/locale/mn/LC_MESSAGES/django.po' adding 'django_comments/locale/nb/LC_MESSAGES/django.mo' adding 'django_comments/locale/nb/LC_MESSAGES/django.po' adding 'django_comments/locale/ne/LC_MESSAGES/django.mo' adding 'django_comments/locale/ne/LC_MESSAGES/django.po' adding 'django_comments/locale/nl/LC_MESSAGES/django.mo' adding 'django_comments/locale/nl/LC_MESSAGES/django.po' adding 'django_comments/locale/nn/LC_MESSAGES/django.mo' adding 'django_comments/locale/nn/LC_MESSAGES/django.po' adding 'django_comments/locale/pa/LC_MESSAGES/django.mo' adding 'django_comments/locale/pa/LC_MESSAGES/django.po' adding 'django_comments/locale/pl/LC_MESSAGES/django.mo' adding 'django_comments/locale/pl/LC_MESSAGES/django.po' adding 'django_comments/locale/pt/LC_MESSAGES/django.mo' adding 'django_comments/locale/pt/LC_MESSAGES/django.po' adding 'django_comments/locale/pt_BR/LC_MESSAGES/django.mo' adding 'django_comments/locale/pt_BR/LC_MESSAGES/django.po' adding 'django_comments/locale/ro/LC_MESSAGES/django.mo' adding 'django_comments/locale/ro/LC_MESSAGES/django.po' adding 'django_comments/locale/ru/LC_MESSAGES/django.mo' adding 'django_comments/locale/ru/LC_MESSAGES/django.po' adding 'django_comments/locale/sk/LC_MESSAGES/django.mo' adding 'django_comments/locale/sk/LC_MESSAGES/django.po' adding 'django_comments/locale/sl/LC_MESSAGES/django.mo' adding 'django_comments/locale/sl/LC_MESSAGES/django.po' adding 'django_comments/locale/sq/LC_MESSAGES/django.mo' adding 'django_comments/locale/sq/LC_MESSAGES/django.po' adding 'django_comments/locale/sr/LC_MESSAGES/django.mo' adding 'django_comments/locale/sr/LC_MESSAGES/django.po' adding 'django_comments/locale/sr_Latn/LC_MESSAGES/django.mo' adding 'django_comments/locale/sr_Latn/LC_MESSAGES/django.po' adding 'django_comments/locale/sv/LC_MESSAGES/django.mo' adding 'django_comments/locale/sv/LC_MESSAGES/django.po' adding 'django_comments/locale/sw/LC_MESSAGES/django.mo' adding 'django_comments/locale/sw/LC_MESSAGES/django.po' adding 'django_comments/locale/ta/LC_MESSAGES/django.mo' adding 'django_comments/locale/ta/LC_MESSAGES/django.po' adding 'django_comments/locale/te/LC_MESSAGES/django.mo' adding 'django_comments/locale/te/LC_MESSAGES/django.po' adding 'django_comments/locale/th/LC_MESSAGES/django.mo' adding 'django_comments/locale/th/LC_MESSAGES/django.po' adding 'django_comments/locale/tr/LC_MESSAGES/django.mo' adding 'django_comments/locale/tr/LC_MESSAGES/django.po' adding 'django_comments/locale/tt/LC_MESSAGES/django.mo' adding 'django_comments/locale/tt/LC_MESSAGES/django.po' adding 'django_comments/locale/uk/LC_MESSAGES/django.mo' adding 'django_comments/locale/uk/LC_MESSAGES/django.po' adding 'django_comments/locale/ur/LC_MESSAGES/django.mo' adding 'django_comments/locale/ur/LC_MESSAGES/django.po' adding 'django_comments/locale/vi/LC_MESSAGES/django.mo' adding 'django_comments/locale/vi/LC_MESSAGES/django.po' adding 'django_comments/locale/zh_Hans/LC_MESSAGES/django.mo' adding 'django_comments/locale/zh_Hans/LC_MESSAGES/django.po' adding 'django_comments/locale/zh_Hant/LC_MESSAGES/django.mo' adding 'django_comments/locale/zh_Hant/LC_MESSAGES/django.po' adding 'django_comments/management/__init__.py' adding 'django_comments/management/commands/__init__.py' adding 'django_comments/management/commands/delete_stale_comments.py' adding 'django_comments/migrations/0001_initial.py' adding 'django_comments/migrations/0002_update_user_email_field_length.py' adding 'django_comments/migrations/0003_add_submit_date_index.py' adding 'django_comments/migrations/0004_add_object_pk_is_removed_index.py' adding 'django_comments/migrations/__init__.py' adding 'django_comments/templates/comments/400-debug.html' adding 'django_comments/templates/comments/approve.html' adding 'django_comments/templates/comments/approved.html' adding 'django_comments/templates/comments/base.html' adding 'django_comments/templates/comments/delete.html' adding 'django_comments/templates/comments/deleted.html' adding 'django_comments/templates/comments/flag.html' adding 'django_comments/templates/comments/flagged.html' adding 'django_comments/templates/comments/form.html' adding 'django_comments/templates/comments/list.html' adding 'django_comments/templates/comments/posted.html' adding 'django_comments/templates/comments/preview.html' adding 'django_comments/templatetags/__init__.py' adding 'django_comments/templatetags/comments.py' adding 'django_comments/views/__init__.py' adding 'django_comments/views/comments.py' adding 'django_comments/views/moderation.py' adding 'django_comments/views/utils.py' adding 'django_contrib_comments-2.2.0.dist-info/licenses/LICENSE.txt' adding 'django_contrib_comments-2.2.0.dist-info/METADATA' adding 'django_contrib_comments-2.2.0.dist-info/WHEEL' adding 'django_contrib_comments-2.2.0.dist-info/top_level.txt' adding 'django_contrib_comments-2.2.0.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Building wheel for django-contrib-comments (pyproject.toml): finished with status 'done' Created wheel for django-contrib-comments: filename=django_contrib_comments-2.2.0-py3-none-any.whl size=410865 sha256=fd492f65c36058b2ded5154c54828a94d01489f277189a5729668965779c7a7e Stored in directory: /home/pterjan/.cache/pip/wheels/22/2d/cb/0742b4741542bca20b4969c0e1c6daf761e56615d63229b850 Successfully built django-contrib-comments + PYTHONPATH=/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0 + sphinx-build docs html Running Sphinx v8.2.3 loading translations [en]... done making output directory... done WARNING: html_static_path entry '_static' does not exist Converting `source_suffix = '.txt'` to `source_suffix = {'.txt': 'restructuredtext'}`. loading intersphinx inventory 'python' from https://docs.python.org/objects.inv ... loading intersphinx inventory 'django' from https://docs.djangoproject.com/en/stable/objects.inv ... WARNING: failed to reach any of the inventories with the following issues: intersphinx inventory 'https://docs.python.org/objects.inv' not fetchable due to : HTTPSConnectionPool(host='docs.python.org', port=443): Max retries exceeded with url: /objects.inv (Caused by NameResolutionError(": Failed to resolve 'docs.python.org' ([Errno -2] Name or service not known)")) WARNING: failed to reach any of the inventories with the following issues: intersphinx inventory 'https://docs.djangoproject.com/en/stable/objects.inv' not fetchable due to : HTTPSConnectionPool(host='docs.djangoproject.com', port=443): Max retries exceeded with url: /en/stable/objects.inv (Caused by NameResolutionError(": Failed to resolve 'docs.djangoproject.com' ([Errno -2] Name or service not known)")) building [mo]: targets for 0 po files that are out of date writing output... building [html]: targets for 11 source files that are out of date updating environment: [new config] 11 added, 0 changed, 0 removed reading sources... [ 9%] custom reading sources... [ 18%] example reading sources... [ 27%] forms reading sources... [ 36%] index reading sources... [ 45%] management_commands reading sources... [ 55%] models reading sources... [ 64%] moderation reading sources... [ 73%] porting reading sources... [ 82%] quickstart reading sources... [ 91%] settings reading sources... [100%] signals /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/docs/example.txt:1: ERROR: Unknown directive type "highlightlang". .. highlightlang:: html+django [docutils] /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/docs/index.txt:8: ERROR: Unknown directive type "highlightlang". .. highlightlang:: html+django [docutils] looking for now-outdated files... none found pickling environment... done checking consistency... done preparing documents... done copying assets... copying static files... Writing evaluated template result to /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/html/_static/basic.css Writing evaluated template result to /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/html/_static/documentation_options.js Writing evaluated template result to /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/html/_static/language_data.js Writing evaluated template result to /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/html/_static/classic.css Writing evaluated template result to /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/html/_static/sidebar.js copying static files: done copying extra files... copying extra files: done copying assets: done writing output... [ 9%] custom writing output... [ 18%] example writing output... [ 27%] forms writing output... [ 36%] index writing output... [ 45%] management_commands writing output... [ 55%] models writing output... [ 64%] moderation writing output... [ 73%] porting writing output... [ 82%] quickstart writing output... [ 91%] settings writing output... [100%] signals /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/docs/quickstart.txt:9: WARNING: undefined label: 'django:enabling-the-sites-framework' [ref.ref] /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/docs/quickstart.txt:45: WARNING: undefined label: 'loading-custom-template-libraries' [ref.ref] generating indices... genindex py-modindex done writing additional pages... search done dumping search index in English (code: en)... done dumping object inventory... done build succeeded, 7 warnings. The HTML pages are in html. + rm -rf html/.doctrees html/.buildinfo + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.b9aKA6 + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build + '[' 1 -eq 1 ']' + '[' /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT '!=' / ']' + rm -rf /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT ++ dirname /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT + mkdir -p /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build + mkdir /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd django-contrib-comments-2.2.0 + '[' 1 -eq 1 ']' ++ ls /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/pyproject-wheeldir/django_contrib_comments-2.2.0-py3-none-any.whl ++ xargs basename --multiple ++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/' + specifier=django_contrib_comments==2.2.0 + '[' -z django_contrib_comments==2.2.0 ']' + TMPDIR=/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/.pyproject-builddir + /usr/bin/python3 -m pip install --root /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT --prefix /usr --no-deps --disable-pip-version-check --progress-bar off --verbose --ignore-installed --no-warn-script-location --no-index --no-cache-dir --find-links /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/pyproject-wheeldir django_contrib_comments==2.2.0 Using pip 25.0.1 from /usr/lib/python3.13/site-packages/pip (python 3.13) Looking in links: /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/pyproject-wheeldir Processing ./pyproject-wheeldir/django_contrib_comments-2.2.0-py3-none-any.whl Installing collected packages: django_contrib_comments Successfully installed django_contrib_comments-2.2.0 + '[' -d /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/bin ']' + rm -f /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/python-django-contrib-comments-2.2.0-5.mga10.noarch-pyproject-ghost-distinfo + site_dirs=() + '[' -d /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/lib/python3.13/site-packages ']' + site_dirs+=("/usr/lib/python3.13/site-packages") + '[' /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/lib64/python3.13/site-packages '!=' /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/lib/python3.13/site-packages ']' + '[' -d /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/lib64/python3.13/site-packages ']' + for site_dir in ${site_dirs[@]} + for distinfo in /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT$site_dir/*.dist-info + echo '%ghost /usr/lib/python3.13/site-packages/django_contrib_comments-2.2.0.dist-info' + sed -i s/pip/rpm/ /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_contrib_comments-2.2.0.dist-info/INSTALLER + PYTHONPATH=/usr/lib/rpm/redhat + /usr/bin/python3 -B /usr/lib/rpm/redhat/pyproject_preprocess_record.py --buildroot /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT --record /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_contrib_comments-2.2.0.dist-info/RECORD --output /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/python-django-contrib-comments-2.2.0-5.mga10.noarch-pyproject-record + rm -fv /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_contrib_comments-2.2.0.dist-info/RECORD removed '/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_contrib_comments-2.2.0.dist-info/RECORD' + rm -fv /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_contrib_comments-2.2.0.dist-info/REQUESTED removed '/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_contrib_comments-2.2.0.dist-info/REQUESTED' ++ wc -l /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/python-django-contrib-comments-2.2.0-5.mga10.noarch-pyproject-ghost-distinfo ++ cut -f1 '-d ' + lines=1 + '[' 1 -ne 1 ']' + RPM_FILES_ESCAPE=4.19 + /usr/bin/python3 /usr/lib/rpm/redhat/pyproject_save_files.py --output-files /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/python-django-contrib-comments-2.2.0-5.mga10.noarch-pyproject-files --output-modules /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/python-django-contrib-comments-2.2.0-5.mga10.noarch-pyproject-modules --buildroot /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT --sitelib /usr/lib/python3.13/site-packages --sitearch /usr/lib64/python3.13/site-packages --python-version 3.13 --pyproject-record /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/python-django-contrib-comments-2.2.0-5.mga10.noarch-pyproject-record --prefix /usr django_comments + /usr/lib/rpm/check-buildroot + '[' -n '' ']' + /usr/share/spec-helper/clean_files + '[' -n '' ']' + /usr/share/spec-helper/compress_files .xz + '[' -n '' ']' + /usr/share/spec-helper/relink_symlinks + '[' -n '' ']' + /usr/share/spec-helper/clean_perl + '[' -n '' ']' + /usr/share/spec-helper/lib_symlinks + '[' -n '' ']' + /usr/share/spec-helper/gprintify + '[' -n '' ']' + /usr/share/spec-helper/fix_mo + '[' -n '' ']' + /usr/share/spec-helper/fix_pamd + '[' -n '' ']' + /usr/share/spec-helper/remove_info_dir + '[' -n '' ']' + /usr/share/spec-helper/fix_eol + '[' -n '' ']' + /usr/share/spec-helper/check_desktop_files + '[' -n '' ']' + /usr/share/spec-helper/check_elf_files + /usr/lib/rpm/brp-strip /usr/bin/strip + /usr/lib/rpm/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/brp-remove-la-files + /usr/lib/rpm/redhat/brp-mangle-shebangs + env -u SOURCE_DATE_EPOCH /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j16 Bytecompiling .py files below /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/lib/python3.13 using python3.13 Not clamping source mtimes, $SOURCE_DATE_EPOCH not set + /usr/lib/rpm/redhat/brp-python-hardlink Executing(%check): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.etIlbd + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd django-contrib-comments-2.2.0 + '[' 1 -eq 1 ']' + PYTHONWARNINGS=default + /usr/bin/python3 tests/runtests.py /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/django_comments/forms.py:103: RemovedInDjango60Warning: The default scheme will be changed from 'http' to 'https' in Django 6.0. Pass the forms.URLField.assume_scheme argument to silence this warning, or set the FORMS_URLFIELD_ASSUME_HTTPS transitional setting to True to opt into using 'https' as the new default scheme. url = forms.URLField(label=_("URL"), required=False) Creating test database for alias 'default'... Found 115 test(s). System check identified no issues (0 silenced). .................../usr/lib64/python3.13/unittest/case.py:707: DeprecationWarning: It is deprecated to return a value that is not None from a test case (>) return self.run(*args, **kwds) ...................Bad Request: /post/ ............................................/usr/lib64/python3.13/unittest/case.py:707: DeprecationWarning: It is deprecated to return a value that is not None from a test case (>) return self.run(*args, **kwds) ................................. ---------------------------------------------------------------------- Ran 115 tests in 0.913s OK Destroying test database for alias 'default'... + RPM_EC=0 ++ jobs -p + exit 0 Processing files: python3-django-contrib-comments-2.2.0-5.mga10.noarch Executing(%doc): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.d63QDt + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build + cd django-contrib-comments-2.2.0 + DOCDIR=/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/share/doc/python3-django-contrib-comments + export LC_ALL=C + LC_ALL=C + export DOCDIR + /usr/bin/mkdir -p /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/share/doc/python3-django-contrib-comments + cp -pr /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/README.rst /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/share/doc/python3-django-contrib-comments + cp -pr /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/html /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/share/doc/python3-django-contrib-comments + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.WGz50q + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build + cd django-contrib-comments-2.2.0 + LICENSEDIR=/home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/share/licenses/python3-django-contrib-comments + export LC_ALL=C + LC_ALL=C + export LICENSEDIR + /usr/bin/mkdir -p /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/share/licenses/python3-django-contrib-comments + cp -pr /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/django-contrib-comments-2.2.0/LICENSE.txt /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT/usr/share/licenses/python3-django-contrib-comments + RPM_EC=0 ++ jobs -p + exit 0 Provides: python-django-contrib-comments = 2.2.0-5.mga10 python3-django-contrib-comments = 2.2.0-5.mga10 python3.13-django-contrib-comments = 2.2.0-5.mga10 python3.13dist(django-contrib-comments) = 2.2 python3dist(django-contrib-comments) = 2.2 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: python(abi) = 3.13 python3.13dist(django) >= 2.2 Obsoletes: python-django-contrib-comments < 2.2.0-5.mga10 Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build/BUILDROOT Wrote: /home/pterjan/rpmbuild/RPMS/noarch/python3-django-contrib-comments-2.2.0-5.mga10.noarch.rpm Executing(rmbuild): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.jaYYuu + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build + test -d /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build + rm -rf /home/pterjan/rpmbuild/BUILD/python-django-contrib-comments-2.2.0-build + RPM_EC=0 ++ jobs -p + exit 0 D: [iurt_root_command] Success!