Mock Version: 5.5
Mock Version: 5.5
Mock Version: 5.5
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/f40-build-121817-6719/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=<mockbuild.trace_decorator.getLog object at 0xffffff9a810f50>timeout=864000uid=997gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.__4z2khe:/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']unshare_net=TrueprintOutput=False)
Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.__4z2khe:/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', 'c32622173c324e988120b4c3abaad8fd', '-D', '/var/lib/mock/f40-build-121817-6719/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.__4z2khe:/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;<mock-chroot>\\007"', '--setenv=PS1=<mock-chroot> \\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;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\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=1706227200
Wrote: /builddir/build/SRPMS/python-django-contrib-comments-2.0.0-12.fc40.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/f40-build-121817-6719/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=<mockbuild.trace_decorator.getLog object at 0xffffff9a810f50>timeout=864000uid=997gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.__4z2khe:/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']unshare_net=TrueprintOutput=False)
Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.__4z2khe:/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', 'cd97a5cf1eff47df9c3fc01d937c15a5', '-D', '/var/lib/mock/f40-build-121817-6719/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.__4z2khe:/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;<mock-chroot>\\007"', '--setenv=PS1=<mock-chroot> \\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;<mock-chroot>\\007"', 'PS1': '<mock-chroot> \\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=1706227200
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.rwFY7B
+ umask 022
+ cd /builddir/build/BUILD
+ cd /builddir/build/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
+ rm -rf /builddir/build/BUILD/django-contrib-comments-2.0.0-SPECPARTS
+ /usr/bin/mkdir -p /builddir/build/BUILD/django-contrib-comments-2.0.0-SPECPARTS
+ /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.bhtWkH
+ umask 022
+ cd /builddir/build/BUILD
+ CFLAGS='-O2  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer -I/usr/lib/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer -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-errors -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  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer '
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed   -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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'
running build
running build_py
creating build
creating build/lib
creating build/lib/django_comments
copying django_comments/compat.py -> build/lib/django_comments
copying django_comments/forms.py -> build/lib/django_comments
copying django_comments/models.py -> build/lib/django_comments
copying django_comments/abstracts.py -> build/lib/django_comments
copying django_comments/moderation.py -> build/lib/django_comments
copying django_comments/feeds.py -> build/lib/django_comments
copying django_comments/__init__.py -> build/lib/django_comments
copying django_comments/urls.py -> build/lib/django_comments
copying django_comments/managers.py -> build/lib/django_comments
copying django_comments/admin.py -> build/lib/django_comments
copying django_comments/signals.py -> build/lib/django_comments
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/moderation.py -> build/lib/django_comments/views
copying django_comments/views/utils.py -> 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
creating 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
copying django_comments/migrations/0002_update_user_email_field_length.py -> build/lib/django_comments/migrations
copying django_comments/migrations/0001_initial.py -> build/lib/django_comments/migrations
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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'django_comments.locale.es_AR.LC_MESSAGES' is absent from the `packages` configuration.
!!
        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'django_comments.locale.es_AR.LC_MESSAGES' as an importable package[^1],
        but it is absent from setuptools' `packages` configuration.
        This leads to an ambiguous overall configuration. If you want to distribute this
        package, please make sure that 'django_comments.locale.es_AR.LC_MESSAGES' is explicitly added
        to the `packages` configuration field.
        Alternatively, you can also rely on setuptools' discovery methods
        (for example by using `find_namespace_packages(...)`/`find_namespace:`
        instead of `find_packages(...)`/`find:`).
        You can read more about "package discovery" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
        If you don't want 'django_comments.locale.es_AR.LC_MESSAGES' to be distributed and are
        already explicitly excluding 'django_comments.locale.es_AR.LC_MESSAGES' via
        `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
        you can try to use `exclude_package_data`, or `include-package-data=False` in
        combination with a more fine grained `package-data` configuration.
        You can read more about "package data files" on setuptools documentation page:
        - https://setuptools.pypa.io/en/latest/userguide/datafiles.html
        [^1]: For Python, any directory (with suitable naming) can be imported,
              even if it does not contain any `.py` files.
              On the other hand, currently there is no concept of package data
              directory, all directories are treated like packages.
        ********************************************************************************
!!
  check.warn(importable)
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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)
creating build/lib/django_comments/locale
creating build/lib/django_comments/locale/af
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
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
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
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
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
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
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
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
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
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
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
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
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
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
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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.12/site-packages/setuptools/command/build_py.py:207: _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/el/LC_MESSAGES/django.po -> build/lib/django_comments/locale/el/LC_MESSAGES
creating build/lib/django_comments/locale/en
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
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
creating build/lib/django_comments/locale/eo/LC_MESSAGES
copying django_comments/locale/eo/LC_MESSAGES/django.mo -> build/lib/django_comments/locale/eo/LC_MESSAGES
copying django_comments/locale/eo/LC_MESSAGES/django.po -> build/lib/django_comments/locale/eo/LC_MESSAGES
creating build/lib/django_comments/locale/es
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.YxJ1SA
+ umask 022
+ cd /builddir/build/BUILD
+ '[' /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch '!=' / ']'
+ rm -rf /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch
++ dirname /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch
+ mkdir -p /builddir/build/BUILDROOT
+ mkdir /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch
+ CFLAGS='-O2  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer -I/usr/lib/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer -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-errors -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  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer '
+ LDFLAGS='-Wl,-z,relro -Wl,--as-needed   -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch --prefix /usr
running install
/usr/lib/python3.12/site-packages/setuptools/_distutils/cmd.py:66: 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/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments
copying build/lib/django_comments/compat.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates/comments
copying build/lib/django_comments/templates/comments/flagged.html -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates/comments
copying build/lib/django_comments/templates/comments/400-debug.html -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates/comments
copying build/lib/django_comments/templates/comments/flag.html -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates/comments
copying build/lib/django_comments/templates/comments/deleted.html -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates/comments
copying build/lib/django_comments/templates/comments/posted.html -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates/comments
copying build/lib/django_comments/templates/comments/delete.html -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates/comments
copying build/lib/django_comments/templates/comments/list.html -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates/comments
copying build/lib/django_comments/templates/comments/form.html -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates/comments
copying build/lib/django_comments/templates/comments/approve.html -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates/comments
copying build/lib/django_comments/templates/comments/preview.html -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates/comments
copying build/lib/django_comments/templates/comments/approved.html -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates/comments
copying build/lib/django_comments/templates/comments/base.html -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templates/comments
copying build/lib/django_comments/forms.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments
copying build/lib/django_comments/models.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templatetags
copying build/lib/django_comments/templatetags/__init__.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templatetags
copying build/lib/django_comments/templatetags/comments.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templatetags
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/views
copying build/lib/django_comments/views/moderation.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/views
copying build/lib/django_comments/views/utils.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/views
copying build/lib/django_comments/views/__init__.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/views
copying build/lib/django_comments/views/comments.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/views
copying build/lib/django_comments/abstracts.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments
copying build/lib/django_comments/moderation.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments
copying build/lib/django_comments/feeds.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/be
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/be/LC_MESSAGES
copying build/lib/django_comments/locale/be/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/be/LC_MESSAGES
copying build/lib/django_comments/locale/be/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/be/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/eo
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/eo/LC_MESSAGES
copying build/lib/django_comments/locale/eo/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/eo/LC_MESSAGES
copying build/lib/django_comments/locale/eo/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/eo/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/en_GB
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/en_GB/LC_MESSAGES
copying build/lib/django_comments/locale/en_GB/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/en_GB/LC_MESSAGES
copying build/lib/django_comments/locale/en_GB/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/en_GB/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pt_BR
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pt_BR/LC_MESSAGES
copying build/lib/django_comments/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pt_BR/LC_MESSAGES
copying build/lib/django_comments/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pt_BR/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/it
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/it/LC_MESSAGES
copying build/lib/django_comments/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/it/LC_MESSAGES
copying build/lib/django_comments/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/it/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/es
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/es/LC_MESSAGES
copying build/lib/django_comments/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/es/LC_MESSAGES
copying build/lib/django_comments/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/es/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/uk
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/uk/LC_MESSAGES
copying build/lib/django_comments/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/uk/LC_MESSAGES
copying build/lib/django_comments/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/uk/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ca
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ca/LC_MESSAGES
copying build/lib/django_comments/locale/ca/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ca/LC_MESSAGES
copying build/lib/django_comments/locale/ca/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ca/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/lt
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/lt/LC_MESSAGES
copying build/lib/django_comments/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/lt/LC_MESSAGES
copying build/lib/django_comments/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/lt/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/cs
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/cs/LC_MESSAGES
copying build/lib/django_comments/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/cs/LC_MESSAGES
copying build/lib/django_comments/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/cs/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/gd
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/gd/LC_MESSAGES
copying build/lib/django_comments/locale/gd/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/gd/LC_MESSAGES
copying build/lib/django_comments/locale/gd/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/gd/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ta
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ta/LC_MESSAGES
copying build/lib/django_comments/locale/ta/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ta/LC_MESSAGES
copying build/lib/django_comments/locale/ta/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ta/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/he
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/he/LC_MESSAGES
copying build/lib/django_comments/locale/he/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/he/LC_MESSAGES
copying build/lib/django_comments/locale/he/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/he/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ja
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ja/LC_MESSAGES
copying build/lib/django_comments/locale/ja/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ja/LC_MESSAGES
copying build/lib/django_comments/locale/ja/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ja/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/hi
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/hi/LC_MESSAGES
copying build/lib/django_comments/locale/hi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/hi/LC_MESSAGES
copying build/lib/django_comments/locale/hi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/hi/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/nl
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/nl/LC_MESSAGES
copying build/lib/django_comments/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/nl/LC_MESSAGES
copying build/lib/django_comments/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/nl/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fa
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fa/LC_MESSAGES
copying build/lib/django_comments/locale/fa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fa/LC_MESSAGES
copying build/lib/django_comments/locale/fa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fa/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pl
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pl/LC_MESSAGES
copying build/lib/django_comments/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pl/LC_MESSAGES
copying build/lib/django_comments/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pl/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ko
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ko/LC_MESSAGES
copying build/lib/django_comments/locale/ko/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ko/LC_MESSAGES
copying build/lib/django_comments/locale/ko/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ko/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sr_Latn
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sr_Latn/LC_MESSAGES
copying build/lib/django_comments/locale/sr_Latn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sr_Latn/LC_MESSAGES
copying build/lib/django_comments/locale/sr_Latn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sr_Latn/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fi
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fi/LC_MESSAGES
copying build/lib/django_comments/locale/fi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fi/LC_MESSAGES
copying build/lib/django_comments/locale/fi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fi/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sv
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sv/LC_MESSAGES
copying build/lib/django_comments/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sv/LC_MESSAGES
copying build/lib/django_comments/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sv/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/id
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/id/LC_MESSAGES
copying build/lib/django_comments/locale/id/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/id/LC_MESSAGES
copying build/lib/django_comments/locale/id/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/id/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ro
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ro/LC_MESSAGES
copying build/lib/django_comments/locale/ro/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ro/LC_MESSAGES
copying build/lib/django_comments/locale/ro/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ro/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sl
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sl/LC_MESSAGES
copying build/lib/django_comments/locale/sl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sl/LC_MESSAGES
copying build/lib/django_comments/locale/sl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sl/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ur
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ur/LC_MESSAGES
copying build/lib/django_comments/locale/ur/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ur/LC_MESSAGES
copying build/lib/django_comments/locale/ur/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ur/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/es_AR
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/es_AR/LC_MESSAGES
copying build/lib/django_comments/locale/es_AR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/es_AR/LC_MESSAGES
copying build/lib/django_comments/locale/es_AR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/es_AR/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/zh_Hant
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/zh_Hant/LC_MESSAGES
copying build/lib/django_comments/locale/zh_Hant/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/zh_Hant/LC_MESSAGES
copying build/lib/django_comments/locale/zh_Hant/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/zh_Hant/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/lv
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/lv/LC_MESSAGES
copying build/lib/django_comments/locale/lv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/lv/LC_MESSAGES
copying build/lib/django_comments/locale/lv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/lv/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/bg
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/bg/LC_MESSAGES
copying build/lib/django_comments/locale/bg/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/bg/LC_MESSAGES
copying build/lib/django_comments/locale/bg/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/bg/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/bn
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/bn/LC_MESSAGES
copying build/lib/django_comments/locale/bn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/bn/LC_MESSAGES
copying build/lib/django_comments/locale/bn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/bn/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/nn
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/nn/LC_MESSAGES
copying build/lib/django_comments/locale/nn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/nn/LC_MESSAGES
copying build/lib/django_comments/locale/nn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/nn/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/hu
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/hu/LC_MESSAGES
copying build/lib/django_comments/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/hu/LC_MESSAGES
copying build/lib/django_comments/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/hu/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/es_MX
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/es_MX/LC_MESSAGES
copying build/lib/django_comments/locale/es_MX/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/es_MX/LC_MESSAGES
copying build/lib/django_comments/locale/es_MX/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/es_MX/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/el
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/el/LC_MESSAGES
copying build/lib/django_comments/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/el/LC_MESSAGES
copying build/lib/django_comments/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/el/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sr
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sr/LC_MESSAGES
copying build/lib/django_comments/locale/sr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sr/LC_MESSAGES
copying build/lib/django_comments/locale/sr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sr/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/kk
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/kk/LC_MESSAGES
copying build/lib/django_comments/locale/kk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/kk/LC_MESSAGES
copying build/lib/django_comments/locale/kk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/kk/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/eu
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/eu/LC_MESSAGES
copying build/lib/django_comments/locale/eu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/eu/LC_MESSAGES
copying build/lib/django_comments/locale/eu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/eu/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/gl
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/gl/LC_MESSAGES
copying build/lib/django_comments/locale/gl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/gl/LC_MESSAGES
copying build/lib/django_comments/locale/gl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/gl/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/vi
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/vi/LC_MESSAGES
copying build/lib/django_comments/locale/vi/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/vi/LC_MESSAGES
copying build/lib/django_comments/locale/vi/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/vi/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sq
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sq/LC_MESSAGES
copying build/lib/django_comments/locale/sq/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sq/LC_MESSAGES
copying build/lib/django_comments/locale/sq/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sq/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/de
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/de/LC_MESSAGES
copying build/lib/django_comments/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/de/LC_MESSAGES
copying build/lib/django_comments/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/de/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/mn
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/mn/LC_MESSAGES
copying build/lib/django_comments/locale/mn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/mn/LC_MESSAGES
copying build/lib/django_comments/locale/mn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/mn/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ia
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ia/LC_MESSAGES
copying build/lib/django_comments/locale/ia/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ia/LC_MESSAGES
copying build/lib/django_comments/locale/ia/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ia/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sk
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sk/LC_MESSAGES
copying build/lib/django_comments/locale/sk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sk/LC_MESSAGES
copying build/lib/django_comments/locale/sk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sk/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/nb
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/nb/LC_MESSAGES
copying build/lib/django_comments/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/nb/LC_MESSAGES
copying build/lib/django_comments/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/nb/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/km
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/km/LC_MESSAGES
copying build/lib/django_comments/locale/km/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/km/LC_MESSAGES
copying build/lib/django_comments/locale/km/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/km/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/th
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/th/LC_MESSAGES
copying build/lib/django_comments/locale/th/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/th/LC_MESSAGES
copying build/lib/django_comments/locale/th/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/th/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ga
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ga/LC_MESSAGES
copying build/lib/django_comments/locale/ga/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ga/LC_MESSAGES
copying build/lib/django_comments/locale/ga/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ga/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/br
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/br/LC_MESSAGES
copying build/lib/django_comments/locale/br/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/br/LC_MESSAGES
copying build/lib/django_comments/locale/br/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/br/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ru
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ru/LC_MESSAGES
copying build/lib/django_comments/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ru/LC_MESSAGES
copying build/lib/django_comments/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ru/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pt
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pt/LC_MESSAGES
copying build/lib/django_comments/locale/pt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pt/LC_MESSAGES
copying build/lib/django_comments/locale/pt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pt/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ne
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ne/LC_MESSAGES
copying build/lib/django_comments/locale/ne/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ne/LC_MESSAGES
copying build/lib/django_comments/locale/ne/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ne/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/cy
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/cy/LC_MESSAGES
copying build/lib/django_comments/locale/cy/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/cy/LC_MESSAGES
copying build/lib/django_comments/locale/cy/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/cy/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/da
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/da/LC_MESSAGES
copying build/lib/django_comments/locale/da/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/da/LC_MESSAGES
copying build/lib/django_comments/locale/da/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/da/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fy_NL
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fy_NL/LC_MESSAGES
copying build/lib/django_comments/locale/fy_NL/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fy_NL/LC_MESSAGES
copying build/lib/django_comments/locale/fy_NL/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fy_NL/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/af
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/af/LC_MESSAGES
copying build/lib/django_comments/locale/af/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/af/LC_MESSAGES
copying build/lib/django_comments/locale/af/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/af/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ml
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ml/LC_MESSAGES
copying build/lib/django_comments/locale/ml/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ml/LC_MESSAGES
copying build/lib/django_comments/locale/ml/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ml/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fr
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fr/LC_MESSAGES
copying build/lib/django_comments/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fr/LC_MESSAGES
copying build/lib/django_comments/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/fr/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pa
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pa/LC_MESSAGES
copying build/lib/django_comments/locale/pa/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pa/LC_MESSAGES
copying build/lib/django_comments/locale/pa/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/pa/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/en
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/en/LC_MESSAGES
copying build/lib/django_comments/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/en/LC_MESSAGES
copying build/lib/django_comments/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/en/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/az
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/az/LC_MESSAGES
copying build/lib/django_comments/locale/az/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/az/LC_MESSAGES
copying build/lib/django_comments/locale/az/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/az/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/is
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/is/LC_MESSAGES
copying build/lib/django_comments/locale/is/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/is/LC_MESSAGES
copying build/lib/django_comments/locale/is/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/is/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/tt
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/tt/LC_MESSAGES
copying build/lib/django_comments/locale/tt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/tt/LC_MESSAGES
copying build/lib/django_comments/locale/tt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/tt/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/tr
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/tr/LC_MESSAGES
copying build/lib/django_comments/locale/tr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/tr/LC_MESSAGES
copying build/lib/django_comments/locale/tr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/tr/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/mk
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/mk/LC_MESSAGES
copying build/lib/django_comments/locale/mk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/mk/LC_MESSAGES
copying build/lib/django_comments/locale/mk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/mk/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sw
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sw/LC_MESSAGES
copying build/lib/django_comments/locale/sw/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sw/LC_MESSAGES
copying build/lib/django_comments/locale/sw/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/sw/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/bs
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/bs/LC_MESSAGES
copying build/lib/django_comments/locale/bs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/bs/LC_MESSAGES
copying build/lib/django_comments/locale/bs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/bs/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/hr
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/hr/LC_MESSAGES
copying build/lib/django_comments/locale/hr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/hr/LC_MESSAGES
copying build/lib/django_comments/locale/hr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/hr/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ka
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ka/LC_MESSAGES
copying build/lib/django_comments/locale/ka/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ka/LC_MESSAGES
copying build/lib/django_comments/locale/ka/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ka/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/te
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/te/LC_MESSAGES
copying build/lib/django_comments/locale/te/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/te/LC_MESSAGES
copying build/lib/django_comments/locale/te/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/te/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/et
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/et/LC_MESSAGES
copying build/lib/django_comments/locale/et/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/et/LC_MESSAGES
copying build/lib/django_comments/locale/et/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/et/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/zh_Hans
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/zh_Hans/LC_MESSAGES
copying build/lib/django_comments/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/zh_Hans/LC_MESSAGES
copying build/lib/django_comments/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/zh_Hans/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ar
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ar/LC_MESSAGES
copying build/lib/django_comments/locale/ar/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ar/LC_MESSAGES
copying build/lib/django_comments/locale/ar/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/ar/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/kn
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/kn/LC_MESSAGES
copying build/lib/django_comments/locale/kn/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/kn/LC_MESSAGES
copying build/lib/django_comments/locale/kn/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/locale/kn/LC_MESSAGES
creating /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/migrations
copying build/lib/django_comments/migrations/0003_add_submit_date_index.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/migrations
copying build/lib/django_comments/migrations/__init__.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/migrations
copying build/lib/django_comments/migrations/0002_update_user_email_field_length.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/migrations
copying build/lib/django_comments/migrations/0001_initial.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/migrations
copying build/lib/django_comments/__init__.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments
copying build/lib/django_comments/urls.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments
copying build/lib/django_comments/managers.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments
copying build/lib/django_comments/admin.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments
copying build/lib/django_comments/signals.py -> /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/compat.py to compat.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/forms.py to forms.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/models.py to models.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templatetags/__init__.py to __init__.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/templatetags/comments.py to comments.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/views/moderation.py to moderation.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/views/utils.py to utils.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/views/__init__.py to __init__.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/views/comments.py to comments.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/abstracts.py to abstracts.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/moderation.py to moderation.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/feeds.py to feeds.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/migrations/0003_add_submit_date_index.py to 0003_add_submit_date_index.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/migrations/__init__.py to __init__.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/migrations/0002_update_user_email_field_length.py to 0002_update_user_email_field_length.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/migrations/0001_initial.py to 0001_initial.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/__init__.py to __init__.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/urls.py to urls.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/managers.py to managers.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/admin.py to admin.cpython-312.pyc
byte-compiling /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_comments/signals.py to signals.cpython-312.pyc
writing byte-compilation script '/tmp/tmpm1ujiln7.py'
/usr/bin/python3 /tmp/tmpm1ujiln7.py
removing /tmp/tmpm1ujiln7.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/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12/site-packages/django_contrib_comments-2.0.0-py3.12.egg-info
running install_scripts
+ rm -rfv /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/bin/__pycache__
+ /usr/bin/find-debuginfo -j32 --strict-build-id -m -i --build-id-seed 2.0.0-12.fc40 --unique-debug-suffix -2.0.0-12.fc40.noarch --unique-debug-src-base python-django-contrib-comments-2.0.0-12.fc40.noarch --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 50000000 -S debugsourcefiles.list /builddir/build/BUILD/django-contrib-comments-2.0.0
find-debuginfo: starting
Extracting debug info from 0 files
Creating .debug symlinks for symlinks to ELF files
find: ‘debug’: No such file or directory
find-debuginfo: done
+ /usr/lib/rpm/check-buildroot
+ /usr/lib/rpm/redhat/brp-ldconfig
+ /usr/lib/rpm/brp-compress
+ /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
+ env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j32
Bytecompiling .py files below /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/lib/python3.12 using python3.12
+ /usr/lib/rpm/redhat/brp-python-hardlink
Executing(%check): /bin/sh -e /var/tmp/rpm-tmp.BsXoYf
+ umask 022
+ cd /builddir/build/BUILD
+ CFLAGS='-O2  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer '
+ export CFLAGS
+ CXXFLAGS='-O2  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer '
+ export CXXFLAGS
+ FFLAGS='-O2  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer -I/usr/lib/gfortran/modules '
+ export FFLAGS
+ FCFLAGS='-O2  -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  -fasynchronous-unwind-tables -fno-omit-frame-pointer -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-errors -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
+ /usr/bin/python3 setup.py test
running test
WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox.
/usr/lib/python3.12/site-packages/setuptools/command/test.py:193: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!
        ********************************************************************************
        Requirements should be satisfied by a PEP 517 installer.
        If you are using pip, you can try `pip install --use-pep517`.
        ********************************************************************************
!!
  ir_d = dist.fetch_build_eggs(dist.install_requires)
WARNING: The wheel package is not available.
/usr/lib/python3.12/site-packages/setuptools/command/test.py:194: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!
        ********************************************************************************
        Requirements should be satisfied by a PEP 517 installer.
        If you are using pip, you can try `pip install --use-pep517`.
        ********************************************************************************
!!
  tr_d = dist.fetch_build_eggs(dist.tests_require or [])
WARNING: The wheel package is not available.
/usr/lib/python3.12/site-packages/setuptools/command/test.py:195: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!
        ********************************************************************************
        Requirements should be satisfied by a PEP 517 installer.
        If you are using pip, you can try `pip install --use-pep517`.
        ********************************************************************************
!!
  er_d = dist.fetch_build_eggs(
WARNING: The wheel package is not available.
running egg_info
writing django_contrib_comments.egg-info/PKG-INFO
writing dependency_links to django_contrib_comments.egg-info/dependency_links.txt
writing requirements to django_contrib_comments.egg-info/requires.txt
writing top-level names to django_contrib_comments.egg-info/top_level.txt
reading manifest file 'django_contrib_comments.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no previously-included files matching '__pycache__' found under directory '*'
warning: no previously-included files matching '*.py[co]' found under directory '*'
adding license file 'LICENSE.txt'
writing manifest file 'django_contrib_comments.egg-info/SOURCES.txt'
running build_ext
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).
....................Bad Request: /post/
Bad Request: /post/
.Bad Request: /post/
Bad Request: /post/
.................Bad Request: /post/
Bad Request: /post/
Bad Request: /post/
.Bad Request: /post/
...Bad Request: /post/
.Bad Request: /post/
.Method Not Allowed (GET): /post/
.Bad Request: /post/
.Bad Request: /post/
.Bad Request: /post/
.Bad Request: /post/
...Bad Request: /post/
............................................................
----------------------------------------------------------------------
Ran 111 tests in 17.328s
OK
Destroying test database for alias 'default'...
+ RPM_EC=0
++ jobs -p
+ exit 0
Processing files: python3-django-contrib-comments-2.0.0-12.fc40.noarch
Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.5OboaG
+ umask 022
+ cd /builddir/build/BUILD
+ cd django-contrib-comments-2.0.0
+ DOCDIR=/builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/share/doc/python3-django-contrib-comments
+ export LC_ALL=
+ LC_ALL=
+ export DOCDIR
+ /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/share/doc/python3-django-contrib-comments
+ cp -pr /builddir/build/BUILD/django-contrib-comments-2.0.0/README.rst /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/share/doc/python3-django-contrib-comments
+ RPM_EC=0
++ jobs -p
+ exit 0
Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.oaHzAG
+ umask 022
+ cd /builddir/build/BUILD
+ cd django-contrib-comments-2.0.0
+ LICENSEDIR=/builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/share/licenses/python3-django-contrib-comments
+ export LC_ALL=
+ LC_ALL=
+ export LICENSEDIR
+ /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/share/licenses/python3-django-contrib-comments
+ cp -pr /builddir/build/BUILD/django-contrib-comments-2.0.0/LICENSE.txt /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch/usr/share/licenses/python3-django-contrib-comments
+ RPM_EC=0
++ jobs -p
+ exit 0
Provides: python-django-contrib-comments = 2.0.0-12.fc40 python3-django-contrib-comments = 2.0.0-12.fc40 python3.12-django-contrib-comments = 2.0.0-12.fc40 python3.12dist(django-contrib-comments) = 2 python3dist(django-contrib-comments) = 2
Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1
Requires: python(abi) = 3.12 python3.12dist(django) >= 1.11
Obsoletes: python-django-contrib-comments < 2.0.0-12.fc40
Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/python-django-contrib-comments-2.0.0-12.fc40.noarch
Wrote: /builddir/build/RPMS/python3-django-contrib-comments-2.0.0-12.fc40.noarch.rpm
Child return code was: 0