Mock Version: 6.1 Mock Version: 6.1 Mock Version: 6.1 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-contrib-comments.spec'], chrootPath='/var/lib/mock/f43-build-58339523-6564590/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=201600uid=1000gid=425user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.bnagcbv3:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.bnagcbv3:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '153151e0cce34e9081daddd0063464bd', '-D', '/var/lib/mock/f43-build-58339523-6564590/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.bnagcbv3:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-contrib-comments.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1737158400 Wrote: /builddir/build/SRPMS/python-django-contrib-comments-2.0.0-17.fc43.src.rpm Child return code was: 0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-contrib-comments.spec'], chrootPath='/var/lib/mock/f43-build-58339523-6564590/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=201600uid=1000gid=425user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.bnagcbv3:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.bnagcbv3:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '3e79ede24baa4b40bfa18233f7b59a34', '-D', '/var/lib/mock/f43-build-58339523-6564590/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.bnagcbv3:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bb --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-contrib-comments.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1737158400 Executing(%mkbuilddir): /bin/sh -e /var/tmp/rpm-tmp.tfpGH0 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.RxX5D8 + umask 022 + cd /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build + cd /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build + rm -rf django-contrib-comments-2.0.0 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/django-contrib-comments-2.0.0.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd django-contrib-comments-2.0.0 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + rm -rf django_contrib_comments.egg-info + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.TNcj3E + umask 022 + cd /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd django-contrib-comments-2.0.0 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -sP' /usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) running build running build_py creating build/lib/django_comments copying django_comments/__init__.py -> build/lib/django_comments copying django_comments/abstracts.py -> build/lib/django_comments copying django_comments/admin.py -> build/lib/django_comments copying django_comments/compat.py -> build/lib/django_comments copying django_comments/feeds.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 copying django_comments/moderation.py -> build/lib/django_comments copying django_comments/signals.py -> build/lib/django_comments copying django_comments/urls.py -> build/lib/django_comments 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/0003_add_submit_date_index.py -> build/lib/django_comments/migrations copying django_comments/migrations/__init__.py -> build/lib/django_comments/migrations creating build/lib/django_comments/templatetags copying django_comments/templatetags/__init__.py -> build/lib/django_comments/templatetags copying django_comments/templatetags/comments.py -> build/lib/django_comments/templatetags creating build/lib/django_comments/views copying django_comments/views/__init__.py -> build/lib/django_comments/views copying django_comments/views/comments.py -> build/lib/django_comments/views copying django_comments/views/moderation.py -> build/lib/django_comments/views copying django_comments/views/utils.py -> build/lib/django_comments/views running egg_info creating django_contrib_comments.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 writing manifest file 'django_contrib_comments.egg-info/SOURCES.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) 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 /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) 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 + RPM_EC=0 ++ jobs -p + exit 0 + umask 022 + cd /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build + '[' /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT '!=' / ']' + rm -rf /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.XoK8ZS ++ dirname /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT + mkdir -p /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build + mkdir /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd django-contrib-comments-2.0.0 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + /usr/bin/python3 setup.py install -O1 --skip-build --root /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT --prefix /usr /usr/lib/python3.13/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) running install /usr/lib/python3.13/site-packages/setuptools/_distutils/cmd.py:90: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. Follow the current Python packaging guidelines when building Python RPM packages. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html and https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ for details. ******************************************************************************** !! self.initialize_options() running install_lib creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments copying build/lib/django_comments/__init__.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments copying build/lib/django_comments/abstracts.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments copying build/lib/django_comments/admin.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments copying build/lib/django_comments/compat.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments copying build/lib/django_comments/feeds.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments copying build/lib/django_comments/forms.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments copying build/lib/django_comments/managers.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments copying build/lib/django_comments/models.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments copying build/lib/django_comments/moderation.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments copying build/lib/django_comments/signals.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments copying build/lib/django_comments/urls.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/migrations copying build/lib/django_comments/migrations/0001_initial.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/migrations copying build/lib/django_comments/migrations/0002_update_user_email_field_length.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/migrations copying build/lib/django_comments/migrations/0003_add_submit_date_index.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/migrations copying build/lib/django_comments/migrations/__init__.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/migrations creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templatetags copying build/lib/django_comments/templatetags/__init__.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templatetags copying build/lib/django_comments/templatetags/comments.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templatetags creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/views copying build/lib/django_comments/views/__init__.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/views copying build/lib/django_comments/views/comments.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/views copying build/lib/django_comments/views/moderation.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/views copying build/lib/django_comments/views/utils.py -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/views creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/af creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/af/LC_MESSAGES copying build/lib/django_comments/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/af/LC_MESSAGES copying build/lib/django_comments/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/af/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ar creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ar/LC_MESSAGES copying build/lib/django_comments/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ar/LC_MESSAGES copying build/lib/django_comments/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ar/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/az creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/az/LC_MESSAGES copying build/lib/django_comments/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/az/LC_MESSAGES copying build/lib/django_comments/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/az/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/be creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/be/LC_MESSAGES copying build/lib/django_comments/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/be/LC_MESSAGES copying build/lib/django_comments/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/be/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/bg creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/bg/LC_MESSAGES copying build/lib/django_comments/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/bg/LC_MESSAGES copying build/lib/django_comments/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/bg/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/bn creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/bn/LC_MESSAGES copying build/lib/django_comments/locale/bn/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/bn/LC_MESSAGES copying build/lib/django_comments/locale/bn/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/bn/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/br creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/br/LC_MESSAGES copying build/lib/django_comments/locale/br/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/br/LC_MESSAGES copying build/lib/django_comments/locale/br/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/br/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/bs creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/bs/LC_MESSAGES copying build/lib/django_comments/locale/bs/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/bs/LC_MESSAGES copying build/lib/django_comments/locale/bs/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/bs/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ca creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ca/LC_MESSAGES copying build/lib/django_comments/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ca/LC_MESSAGES copying build/lib/django_comments/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ca/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/cs creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/cs/LC_MESSAGES copying build/lib/django_comments/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/cs/LC_MESSAGES copying build/lib/django_comments/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/cs/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/cy creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/cy/LC_MESSAGES copying build/lib/django_comments/locale/cy/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/cy/LC_MESSAGES copying build/lib/django_comments/locale/cy/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/cy/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/da creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/da/LC_MESSAGES copying build/lib/django_comments/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/da/LC_MESSAGES copying build/lib/django_comments/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/da/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/de creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/de/LC_MESSAGES copying build/lib/django_comments/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/de/LC_MESSAGES copying build/lib/django_comments/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/de/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/el creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/el/LC_MESSAGES copying build/lib/django_comments/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/el/LC_MESSAGES copying build/lib/django_comments/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/el/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/en creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/en/LC_MESSAGES copying build/lib/django_comments/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/en/LC_MESSAGES copying build/lib/django_comments/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/en/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/en_GB creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/en_GB/LC_MESSAGES copying build/lib/django_comments/locale/en_GB/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/en_GB/LC_MESSAGES copying build/lib/django_comments/locale/en_GB/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/en_GB/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/eo creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/eo/LC_MESSAGES copying build/lib/django_comments/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/eo/LC_MESSAGES copying build/lib/django_comments/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/eo/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/es creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/es/LC_MESSAGES copying build/lib/django_comments/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/es/LC_MESSAGES copying build/lib/django_comments/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/es/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/es_AR creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/es_AR/LC_MESSAGES copying build/lib/django_comments/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/es_AR/LC_MESSAGES copying build/lib/django_comments/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/es_AR/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/es_MX creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/es_MX/LC_MESSAGES copying build/lib/django_comments/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/es_MX/LC_MESSAGES copying build/lib/django_comments/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/es_MX/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/et creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/et/LC_MESSAGES copying build/lib/django_comments/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/et/LC_MESSAGES copying build/lib/django_comments/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/et/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/eu creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/eu/LC_MESSAGES copying build/lib/django_comments/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/eu/LC_MESSAGES copying build/lib/django_comments/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/eu/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fa creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fa/LC_MESSAGES copying build/lib/django_comments/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fa/LC_MESSAGES copying build/lib/django_comments/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fa/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fi creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fi/LC_MESSAGES copying build/lib/django_comments/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fi/LC_MESSAGES copying build/lib/django_comments/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fi/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fr creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fr/LC_MESSAGES copying build/lib/django_comments/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fr/LC_MESSAGES copying build/lib/django_comments/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fr/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fy_NL creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fy_NL/LC_MESSAGES copying build/lib/django_comments/locale/fy_NL/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fy_NL/LC_MESSAGES copying build/lib/django_comments/locale/fy_NL/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/fy_NL/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ga creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ga/LC_MESSAGES copying build/lib/django_comments/locale/ga/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ga/LC_MESSAGES copying build/lib/django_comments/locale/ga/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ga/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/gd creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/gd/LC_MESSAGES copying build/lib/django_comments/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/gd/LC_MESSAGES copying build/lib/django_comments/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/gd/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/gl creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/gl/LC_MESSAGES copying build/lib/django_comments/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/gl/LC_MESSAGES copying build/lib/django_comments/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/gl/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/he creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/he/LC_MESSAGES copying build/lib/django_comments/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/he/LC_MESSAGES copying build/lib/django_comments/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/he/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/hi creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/hi/LC_MESSAGES copying build/lib/django_comments/locale/hi/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/hi/LC_MESSAGES copying build/lib/django_comments/locale/hi/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/hi/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/hr creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/hr/LC_MESSAGES copying build/lib/django_comments/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/hr/LC_MESSAGES copying build/lib/django_comments/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/hr/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/hu creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/hu/LC_MESSAGES copying build/lib/django_comments/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/hu/LC_MESSAGES copying build/lib/django_comments/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/hu/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ia creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ia/LC_MESSAGES copying build/lib/django_comments/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ia/LC_MESSAGES copying build/lib/django_comments/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ia/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/id creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/id/LC_MESSAGES copying build/lib/django_comments/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/id/LC_MESSAGES copying build/lib/django_comments/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/id/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/is creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/is/LC_MESSAGES copying build/lib/django_comments/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/is/LC_MESSAGES copying build/lib/django_comments/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/is/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/it creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/it/LC_MESSAGES copying build/lib/django_comments/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/it/LC_MESSAGES copying build/lib/django_comments/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/it/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ja creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ja/LC_MESSAGES copying build/lib/django_comments/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ja/LC_MESSAGES copying build/lib/django_comments/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ja/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ka creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ka/LC_MESSAGES copying build/lib/django_comments/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ka/LC_MESSAGES copying build/lib/django_comments/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ka/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/kk creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/kk/LC_MESSAGES copying build/lib/django_comments/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/kk/LC_MESSAGES copying build/lib/django_comments/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/kk/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/km creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/km/LC_MESSAGES copying build/lib/django_comments/locale/km/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/km/LC_MESSAGES copying build/lib/django_comments/locale/km/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/km/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/kn creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/kn/LC_MESSAGES copying build/lib/django_comments/locale/kn/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/kn/LC_MESSAGES copying build/lib/django_comments/locale/kn/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/kn/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ko creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ko/LC_MESSAGES copying build/lib/django_comments/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ko/LC_MESSAGES copying build/lib/django_comments/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ko/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/lt creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/lt/LC_MESSAGES copying build/lib/django_comments/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/lt/LC_MESSAGES copying build/lib/django_comments/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/lt/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/lv creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/lv/LC_MESSAGES copying build/lib/django_comments/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/lv/LC_MESSAGES copying build/lib/django_comments/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/lv/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/mk creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/mk/LC_MESSAGES copying build/lib/django_comments/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/mk/LC_MESSAGES copying build/lib/django_comments/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/mk/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ml creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ml/LC_MESSAGES copying build/lib/django_comments/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ml/LC_MESSAGES copying build/lib/django_comments/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ml/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/mn creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/mn/LC_MESSAGES copying build/lib/django_comments/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/mn/LC_MESSAGES copying build/lib/django_comments/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/mn/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/nb creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/nb/LC_MESSAGES copying build/lib/django_comments/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/nb/LC_MESSAGES copying build/lib/django_comments/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/nb/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ne creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ne/LC_MESSAGES copying build/lib/django_comments/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ne/LC_MESSAGES copying build/lib/django_comments/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ne/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/nl creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/nl/LC_MESSAGES copying build/lib/django_comments/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/nl/LC_MESSAGES copying build/lib/django_comments/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/nl/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/nn creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/nn/LC_MESSAGES copying build/lib/django_comments/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/nn/LC_MESSAGES copying build/lib/django_comments/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/nn/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pa creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pa/LC_MESSAGES copying build/lib/django_comments/locale/pa/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pa/LC_MESSAGES copying build/lib/django_comments/locale/pa/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pa/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pl creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pl/LC_MESSAGES copying build/lib/django_comments/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pl/LC_MESSAGES copying build/lib/django_comments/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pl/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pt creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pt/LC_MESSAGES copying build/lib/django_comments/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pt/LC_MESSAGES copying build/lib/django_comments/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pt/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pt_BR creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pt_BR/LC_MESSAGES copying build/lib/django_comments/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pt_BR/LC_MESSAGES copying build/lib/django_comments/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ro creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ro/LC_MESSAGES copying build/lib/django_comments/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ro/LC_MESSAGES copying build/lib/django_comments/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ro/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ru creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ru/LC_MESSAGES copying build/lib/django_comments/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ru/LC_MESSAGES copying build/lib/django_comments/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ru/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sk creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sk/LC_MESSAGES copying build/lib/django_comments/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sk/LC_MESSAGES copying build/lib/django_comments/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sk/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sl creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sl/LC_MESSAGES copying build/lib/django_comments/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sl/LC_MESSAGES copying build/lib/django_comments/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sl/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sq creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sq/LC_MESSAGES copying build/lib/django_comments/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sq/LC_MESSAGES copying build/lib/django_comments/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sq/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sr creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sr/LC_MESSAGES copying build/lib/django_comments/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sr/LC_MESSAGES copying build/lib/django_comments/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sr/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sr_Latn creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sr_Latn/LC_MESSAGES copying build/lib/django_comments/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sr_Latn/LC_MESSAGES copying build/lib/django_comments/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sr_Latn/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sv creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sv/LC_MESSAGES copying build/lib/django_comments/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sv/LC_MESSAGES copying build/lib/django_comments/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sv/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sw creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sw/LC_MESSAGES copying build/lib/django_comments/locale/sw/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sw/LC_MESSAGES copying build/lib/django_comments/locale/sw/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/sw/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ta creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ta/LC_MESSAGES copying build/lib/django_comments/locale/ta/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ta/LC_MESSAGES copying build/lib/django_comments/locale/ta/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ta/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/te creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/te/LC_MESSAGES copying build/lib/django_comments/locale/te/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/te/LC_MESSAGES copying build/lib/django_comments/locale/te/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/te/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/th creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/th/LC_MESSAGES copying build/lib/django_comments/locale/th/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/th/LC_MESSAGES copying build/lib/django_comments/locale/th/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/th/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/tr creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/tr/LC_MESSAGES copying build/lib/django_comments/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/tr/LC_MESSAGES copying build/lib/django_comments/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/tr/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/tt creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/tt/LC_MESSAGES copying build/lib/django_comments/locale/tt/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/tt/LC_MESSAGES copying build/lib/django_comments/locale/tt/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/tt/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/uk creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/uk/LC_MESSAGES copying build/lib/django_comments/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/uk/LC_MESSAGES copying build/lib/django_comments/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/uk/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ur creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ur/LC_MESSAGES copying build/lib/django_comments/locale/ur/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ur/LC_MESSAGES copying build/lib/django_comments/locale/ur/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/ur/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/vi creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/vi/LC_MESSAGES copying build/lib/django_comments/locale/vi/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/vi/LC_MESSAGES copying build/lib/django_comments/locale/vi/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/vi/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/zh_Hans creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/zh_Hans/LC_MESSAGES copying build/lib/django_comments/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/zh_Hans/LC_MESSAGES copying build/lib/django_comments/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/zh_Hant creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/zh_Hant/LC_MESSAGES copying build/lib/django_comments/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/zh_Hant/LC_MESSAGES copying build/lib/django_comments/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/locale/zh_Hant/LC_MESSAGES creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates creating /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/400-debug.html -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/approve.html -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/approved.html -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/base.html -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/delete.html -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/deleted.html -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/flag.html -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/flagged.html -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/form.html -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/list.html -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/posted.html -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates/comments copying build/lib/django_comments/templates/comments/preview.html -> /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templates/comments byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/__init__.py to __init__.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/abstracts.py to abstracts.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/admin.py to admin.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/compat.py to compat.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/feeds.py to feeds.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/forms.py to forms.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/managers.py to managers.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/models.py to models.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/moderation.py to moderation.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/signals.py to signals.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/urls.py to urls.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/migrations/0001_initial.py to 0001_initial.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/migrations/0002_update_user_email_field_length.py to 0002_update_user_email_field_length.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/migrations/0003_add_submit_date_index.py to 0003_add_submit_date_index.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/migrations/__init__.py to __init__.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templatetags/__init__.py to __init__.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templatetags/comments.py to comments.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/views/__init__.py to __init__.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/views/comments.py to comments.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/views/moderation.py to moderation.cpython-313.pyc byte-compiling /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/views/utils.py to utils.cpython-313.pyc writing byte-compilation script '/tmp/tmp82an39nr.py' /usr/bin/python3 /tmp/tmp82an39nr.py removing /tmp/tmp82an39nr.py running install_egg_info 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' Copying django_contrib_comments.egg-info to /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_contrib_comments-2.0.0-py3.13.egg-info running install_scripts + rm -rfv /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/bin/__pycache__ + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-ldconfig + /usr/lib/rpm/brp-compress + /usr/lib/rpm/brp-strip /usr/bin/strip + /usr/lib/rpm/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/redhat/brp-strip-lto /usr/bin/strip + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/redhat/brp-mangle-shebangs + /usr/lib/rpm/brp-remove-la-files + /usr/lib/rpm/redhat/brp-python-rpm-in-distinfo + env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j8 Bytecompiling .py files below /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13 using python3.13 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/bin/add-determinism --brp -j8 /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/migrations/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/migrations/__pycache__/0002_update_user_email_field_length.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templatetags/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/migrations/__pycache__/0003_add_submit_date_index.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/migrations/__pycache__/0001_initial.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/views/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/views/__pycache__/comments.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/views/__pycache__/utils.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/views/__pycache__/moderation.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/templatetags/__pycache__/comments.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/__pycache__/__init__.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/__pycache__/feeds.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/__pycache__/compat.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/__pycache__/managers.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/__pycache__/admin.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/__pycache__/abstracts.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/__pycache__/models.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/__pycache__/signals.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/__pycache__/urls.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/__pycache__/moderation.cpython-313.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/BUILDROOT/usr/lib/python3.13/site-packages/django_comments/__pycache__/forms.cpython-313.pyc: rewriting with normalized contents Scanned 167 directories and 231 files, processed 33 inodes, 21 modified (0 replaced + 21 rewritten), 0 unsupported format, 0 errors Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.ID6XXF + umask 022 + cd /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mcpu=power8 -mtune=power8 -fasynchronous-unwind-tables -fstack-clash-protection -I/usr/lib/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd django-contrib-comments-2.0.0 + PYTHONWARNINGS=default + /usr/bin/python3 tests/runtests.py /builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/django-contrib-comments-2.0.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 111 test(s). System check identified some issues: WARNINGS: custom_comments.CustomComment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_comments.Comment: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. django_comments.CommentFlag: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. testapp.Article: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. testapp.Author: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. testapp.Entry: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the AppConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'. System check identified 6 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/ ..E ====================================================================== ERROR: testPostAsAuthenticatedUser (testapp.tests.test_comment_views.CommentViewTests.testPostAsAuthenticatedUser) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python3.13/site-packages/django/utils/module_loading.py", line 30, in import_string return cached_import(module_path, class_name) File "/usr/lib/python3.13/site-packages/django/utils/module_loading.py", line 16, in cached_import return getattr(module, class_name) AttributeError: module 'django.contrib.auth.hashers' has no attribute 'UnsaltedMD5PasswordHasher' The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/builddir/build/BUILD/python-django-contrib-comments-2.0.0-build/django-contrib-comments-2.0.0/tests/testapp/tests/test_comment_views.py", line 160, in testPostAsAuthenticatedUser self.client.login(username="normaluser", password="normaluser") ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.13/site-packages/django/test/client.py", line 838, in login user = authenticate(**credentials) File "/usr/lib/python3.13/site-packages/django/views/decorators/debug.py", line 75, in sensitive_variables_wrapper return func(*func_args, **func_kwargs) File "/usr/lib/python3.13/site-packages/django/contrib/auth/__init__.py", line 79, in authenticate user = backend.authenticate(request, **credentials) File "/usr/lib/python3.13/site-packages/django/contrib/auth/backends.py", line 48, in authenticate if user.check_password(password) and self.user_can_authenticate(user): ~~~~~~~~~~~~~~~~~~~^^^^^^^^^^ File "/usr/lib/python3.13/site-packages/django/contrib/auth/base_user.py", line 109, in check_password return check_password(raw_password, self.password, setter) File "/usr/lib/python3.13/site-packages/django/contrib/auth/hashers.py", line 80, in check_password is_correct, must_update = verify_password(password, encoded, preferred=preferred) ~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.13/site-packages/django/contrib/auth/hashers.py", line 44, in verify_password preferred = get_hasher(preferred) File "/usr/lib/python3.13/site-packages/django/contrib/auth/hashers.py", line 153, in get_hasher return get_hashers()[0] ~~~~~~~~~~~^^ File "/usr/lib/python3.13/site-packages/django/contrib/auth/hashers.py", line 120, in get_hashers hasher_cls = import_string(hasher_path) File "/usr/lib/python3.13/site-packages/django/utils/module_loading.py", line 32, in import_string raise ImportError( ...<2 lines>... ) from err ImportError: Module "django.contrib.auth.hashers" does not define a "UnsaltedMD5PasswordHasher" attribute/class ---------------------------------------------------------------------- Ran 41 tests in 0.308s FAILED (errors=1) Destroying test database for alias 'default'... RPM build errors: error: Bad exit status from /var/tmp/rpm-tmp.ID6XXF (%check) Bad exit status from /var/tmp/rpm-tmp.ID6XXF (%check) Child return code was: 1 EXCEPTION: [Error('Command failed: \n # /usr/bin/systemd-nspawn -q -M 3e79ede24baa4b40bfa18233f7b59a34 -D /var/lib/mock/f43-build-58339523-6564590/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.bnagcbv3:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin \'--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"\' \'--setenv=PS1= \\s-\\v\\$ \' --setenv=LANG=C.UTF-8 --resolv-conf=off bash --login -c \'/usr/bin/rpmbuild -bb --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-contrib-comments.spec\'\n', 1)] Traceback (most recent call last): File "/usr/lib/python3.13/site-packages/mockbuild/trace_decorator.py", line 93, in trace result = func(*args, **kw) File "/usr/lib/python3.13/site-packages/mockbuild/util.py", line 610, in do_with_status raise exception.Error("Command failed: \n # %s\n%s" % (cmd_pretty(command, env), output), child.returncode) mockbuild.exception.Error: Command failed: # /usr/bin/systemd-nspawn -q -M 3e79ede24baa4b40bfa18233f7b59a34 -D /var/lib/mock/f43-build-58339523-6564590/root -a -u mockbuild --capability=cap_ipc_lock --bind=/tmp/mock-resolv.bnagcbv3:/etc/resolv.conf --bind=/dev/btrfs-control --bind=/dev/mapper/control --bind=/dev/fuse --bind=/dev/loop-control --bind=/dev/loop0 --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4 --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8 --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin '--setenv=PROMPT_COMMAND=printf "\033]0;\007"' '--setenv=PS1= \s-\v\$ ' --setenv=LANG=C.UTF-8 --resolv-conf=off bash --login -c '/usr/bin/rpmbuild -bb --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-contrib-comments.spec'