Mock Version: 6.5 Mock Version: 6.5 Mock Version: 6.5 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-tables2.spec'], chrootPath='/var/lib/mock/f45-build-30471-644/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=864000uid=995gid=135user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.nag4z2tu:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.nag4z2tu:/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', '54d08cb13cc34f338c5594f415b95b87', '-D', '/var/lib/mock/f45-build-30471-644/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.nag4z2tu:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-tables2.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1784160000 Wrote: /builddir/build/SRPMS/python-django-tables2-2.4.0-21.fc45.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-tables2.spec'], chrootPath='/var/lib/mock/f45-build-30471-644/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=864000uid=995gid=135user='mockbuild'unshare_net=TrueprintOutput=Falsenspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.nag4z2tu:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.nag4z2tu:/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', '9154bcb5cfb04d039aeb97d497ef35a7', '-D', '/var/lib/mock/f45-build-30471-644/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.nag4z2tu:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bb --noclean --target noarch --nodeps /builddir/build/SPECS/python-django-tables2.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: noarch Building for target noarch warning: The %py3_build macro is deprecated and will likely stop working in Fedora 45. See the current Python packaging guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ warning: The %py3_install macro is deprecated and will likely stop working in Fedora 45. See the current Python packaging guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ setting SOURCE_DATE_EPOCH=1784160000 Executing(mkbuilddir): /bin/sh -e /var/tmp/rpm-tmp.krM0Ju Creating(rpmbuild.env): /builddir/build/BUILD/python-django-tables2-2.4.0-build/rpmbuild.env RPM_SOURCE_DIR="/builddir/build/SOURCES" RPM_BUILD_DIR="/builddir/build/BUILD/python-django-tables2-2.4.0-build" RPM_OPT_FLAGS="-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wno-complain-wrong-lang -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 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer" RPM_LD_FLAGS="-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 " RPM_ARCH="noarch" RPM_OS="linux" RPM_BUILD_NCPUS="8" RPM_SPECPARTS_DIR="/builddir/build/BUILD/python-django-tables2-2.4.0-build/SPECPARTS" export RPM_SOURCE_DIR RPM_BUILD_DIR RPM_OPT_FLAGS RPM_ARCH RPM_OS RPM_BUILD_NCPUS RPM_SPECPARTS_DIR RPM_LD_FLAGS RPM_DOC_DIR="/usr/share/doc" export RPM_DOC_DIR RPM_PACKAGE_NAME="python-django-tables2" RPM_PACKAGE_VERSION="2.4.0" RPM_PACKAGE_RELEASE="21.fc45" export RPM_PACKAGE_NAME RPM_PACKAGE_VERSION RPM_PACKAGE_RELEASE LANG=C.UTF-8 export LANG unset CDPATH DISPLAY ||: unset DEBUGINFOD_URLS ||: unset RPM_CONFIG_DIR ||: RPM_BUILD_ROOT="/builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT" export RPM_BUILD_ROOT PKG_CONFIG_PATH="${PKG_CONFIG_PATH}:/usr/lib/pkgconfig:/usr/share/pkgconfig" export PKG_CONFIG_PATH CONFIG_SITE=${CONFIG_SITE:-NONE} export CONFIG_SITE Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.Ji6SNV + umask 022 + cd /builddir/build/BUILD/python-django-tables2-2.4.0-build + cd /builddir/build/BUILD/python-django-tables2-2.4.0-build + rm -rf django-tables2-2.4.0 + /usr/bin/rpmuncompress -x /builddir/build/SOURCES/django-tables2-2.4.0.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd django-tables2-2.4.0 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + rm -vr django_tables2.egg-info/ removed 'django_tables2.egg-info/PKG-INFO' removed 'django_tables2.egg-info/SOURCES.txt' removed 'django_tables2.egg-info/dependency_links.txt' removed 'django_tables2.egg-info/requires.txt' removed 'django_tables2.egg-info/top_level.txt' removed directory 'django_tables2.egg-info/' + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.dPvjgT + umask 022 + cd /builddir/build/BUILD/python-django-tables2-2.4.0-build + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-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 -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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-tables2-2.4.0 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -sP' /usr/lib/python3.15/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running build running build_py creating build/lib/django_tables2 copying django_tables2/__init__.py -> build/lib/django_tables2 copying django_tables2/config.py -> build/lib/django_tables2 copying django_tables2/data.py -> build/lib/django_tables2 copying django_tables2/paginators.py -> build/lib/django_tables2 copying django_tables2/rows.py -> build/lib/django_tables2 copying django_tables2/tables.py -> build/lib/django_tables2 copying django_tables2/utils.py -> build/lib/django_tables2 copying django_tables2/views.py -> build/lib/django_tables2 creating build/lib/django_tables2/columns copying django_tables2/columns/__init__.py -> build/lib/django_tables2/columns copying django_tables2/columns/base.py -> build/lib/django_tables2/columns copying django_tables2/columns/booleancolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/checkboxcolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/datecolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/datetimecolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/emailcolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/filecolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/jsoncolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/linkcolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/manytomanycolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/templatecolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/timecolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/urlcolumn.py -> build/lib/django_tables2/columns creating build/lib/django_tables2/export copying django_tables2/export/__init__.py -> build/lib/django_tables2/export copying django_tables2/export/export.py -> build/lib/django_tables2/export copying django_tables2/export/views.py -> build/lib/django_tables2/export creating build/lib/django_tables2/templatetags copying django_tables2/templatetags/__init__.py -> build/lib/django_tables2/templatetags copying django_tables2/templatetags/django_tables2.py -> build/lib/django_tables2/templatetags running egg_info creating django_tables2.egg-info writing django_tables2.egg-info/PKG-INFO writing dependency_links to django_tables2.egg-info/dependency_links.txt writing requirements to django_tables2.egg-info/requires.txt writing top-level names to django_tables2.egg-info/top_level.txt writing manifest file 'django_tables2.egg-info/SOURCES.txt' reading manifest file 'django_tables2.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'docs/pages/CHANGELOG.md' warning: no previously-included files matching '*' found under directory 'docs/_build' adding license file 'LICENSE' writing manifest file 'django_tables2.egg-info/SOURCES.txt' /usr/lib/python3.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.cs.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.cs.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.de.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.de.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.el.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.el.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.en.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.en.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.es.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.es.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.fr.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.fr.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.hu.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.hu.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.it.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.it.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.lt.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.lt.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.nb.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.nb.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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) creating build/lib/django_tables2/locale/cs/LC_MESSAGES copying django_tables2/locale/cs/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/cs/LC_MESSAGES copying django_tables2/locale/cs/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/cs/LC_MESSAGES creating build/lib/django_tables2/locale/de/LC_MESSAGES copying django_tables2/locale/de/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/de/LC_MESSAGES copying django_tables2/locale/de/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/de/LC_MESSAGES creating build/lib/django_tables2/locale/el/LC_MESSAGES copying django_tables2/locale/el/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/el/LC_MESSAGES copying django_tables2/locale/el/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/el/LC_MESSAGES creating build/lib/django_tables2/locale/en/LC_MESSAGES copying django_tables2/locale/en/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/en/LC_MESSAGES copying django_tables2/locale/en/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/en/LC_MESSAGES creating build/lib/django_tables2/locale/es/LC_MESSAGES copying django_tables2/locale/es/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/es/LC_MESSAGES copying django_tables2/locale/es/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/es/LC_MESSAGES creating build/lib/django_tables2/locale/fr/LC_MESSAGES copying django_tables2/locale/fr/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/fr/LC_MESSAGES copying django_tables2/locale/fr/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/fr/LC_MESSAGES creating build/lib/django_tables2/locale/hu/LC_MESSAGES copying django_tables2/locale/hu/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/hu/LC_MESSAGES copying django_tables2/locale/hu/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/hu/LC_MESSAGES creating build/lib/django_tables2/locale/it/LC_MESSAGES copying django_tables2/locale/it/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/it/LC_MESSAGES copying django_tables2/locale/it/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/it/LC_MESSAGES creating build/lib/django_tables2/locale/lt/LC_MESSAGES copying django_tables2/locale/lt/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/lt/LC_MESSAGES copying django_tables2/locale/lt/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/lt/LC_MESSAGES creating build/lib/django_tables2/locale/nb/LC_MESSAGES copying django_tables2/locale/nb/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/nb/LC_MESSAGES copying django_tables2/locale/nb/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/nb/LC_MESSAGES creating build/lib/django_tables2/locale/nl/LC_MESSAGES copying django_tables2/locale/nl/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/nl/LC_MESSAGES copying django_tables2/locale/nl/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/nl/LC_MESSAGES creating build/lib/django_tables2/locale/pl/LC_MESSAGES copying django_tables2/locale/pl/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/pl/LC_MESSAGES copying django_tables2/locale/pl/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/pl/LC_MESSAGES creating build/lib/django_tables2/locale/pt_BR/LC_MESSAGES copying django_tables2/locale/pt_BR/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/pt_BR/LC_MESSAGES /usr/lib/python3.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.nl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.nl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.pl.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.pl.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.pt_BR.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.pt_BR.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.pt_PT.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.locale.pt_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_tables2.locale.pt_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_tables2.locale.pt_PT.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.locale.pt_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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.ru.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.ru.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.sv.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.sv.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.uk.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.uk.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.locale.zh_Hans.LC_MESSAGES' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.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_tables2.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_tables2.locale.zh_Hans.LC_MESSAGES' to be distributed and are already explicitly excluding 'django_tables2.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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.static.django_tables2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2' as an importable package[^1], but it 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_tables2.static.django_tables2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can 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_tables2.static.django_tables2' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` 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.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.static.django_tables2.themes.paleblue.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2.themes.paleblue.css' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2.themes.paleblue.css' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2.themes.paleblue.css' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2.themes.paleblue.css' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.static.django_tables2.themes.paleblue.img' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.static.django_tables2.themes.paleblue.img' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'django_tables2.static.django_tables2.themes.paleblue.img' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'django_tables2.static.django_tables2.themes.paleblue.img' to be distributed and are already explicitly excluding 'django_tables2.static.django_tables2.themes.paleblue.img' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.15/site-packages/setuptools/command/build_py.py:215: _Warning: Package 'django_tables2.templates.django_tables2' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'django_tables2.templates.django_tables2' as an importable package[^1], but it 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_tables2.templates.django_tables2' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can 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_tables2.templates.django_tables2' to be distributed and are already explicitly excluding 'django_tables2.templates.django_tables2' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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_tables2/locale/pt_BR/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/pt_BR/LC_MESSAGES creating build/lib/django_tables2/locale/pt_PT/LC_MESSAGES copying django_tables2/locale/pt_PT/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/pt_PT/LC_MESSAGES copying django_tables2/locale/pt_PT/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/pt_PT/LC_MESSAGES creating build/lib/django_tables2/locale/ru/LC_MESSAGES copying django_tables2/locale/ru/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/ru/LC_MESSAGES copying django_tables2/locale/ru/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/ru/LC_MESSAGES creating build/lib/django_tables2/locale/sv/LC_MESSAGES copying django_tables2/locale/sv/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/sv/LC_MESSAGES copying django_tables2/locale/sv/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/sv/LC_MESSAGES creating build/lib/django_tables2/locale/uk/LC_MESSAGES copying django_tables2/locale/uk/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/uk/LC_MESSAGES copying django_tables2/locale/uk/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/uk/LC_MESSAGES creating build/lib/django_tables2/locale/zh_Hans/LC_MESSAGES copying django_tables2/locale/zh_Hans/LC_MESSAGES/django.mo -> build/lib/django_tables2/locale/zh_Hans/LC_MESSAGES copying django_tables2/locale/zh_Hans/LC_MESSAGES/django.po -> build/lib/django_tables2/locale/zh_Hans/LC_MESSAGES creating build/lib/django_tables2/static/django_tables2 copying django_tables2/static/django_tables2/bootstrap.css -> build/lib/django_tables2/static/django_tables2 creating build/lib/django_tables2/static/django_tables2/themes/paleblue/css copying django_tables2/static/django_tables2/themes/paleblue/css/screen.css -> build/lib/django_tables2/static/django_tables2/themes/paleblue/css creating build/lib/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/arrow-active-down.png -> build/lib/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/arrow-active-up.png -> build/lib/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/arrow-inactive-down.png -> build/lib/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/arrow-inactive-up.png -> build/lib/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/false.gif -> build/lib/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/header-bg.png -> build/lib/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/missing.png -> build/lib/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/pagination-bg.gif -> build/lib/django_tables2/static/django_tables2/themes/paleblue/img copying django_tables2/static/django_tables2/themes/paleblue/img/true.gif -> build/lib/django_tables2/static/django_tables2/themes/paleblue/img creating build/lib/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap-responsive.html -> build/lib/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap.html -> build/lib/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/bootstrap4.html -> build/lib/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/semantic.html -> build/lib/django_tables2/templates/django_tables2 copying django_tables2/templates/django_tables2/table.html -> build/lib/django_tables2/templates/django_tables2 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.qYNoyY + umask 022 + cd /builddir/build/BUILD/python-django-tables2-2.4.0-build + '[' /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT '!=' / ']' + rm -rf /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT ++ dirname /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT + mkdir -p /builddir/build/BUILD/python-django-tables2-2.4.0-build + mkdir /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-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 -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -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-tables2-2.4.0 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -march=rva23u64 -mabi=lp64d -fasynchronous-unwind-tables -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + /usr/bin/python3 setup.py install -O1 --skip-build --root /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT --prefix /usr /usr/lib/python3.15/site-packages/setuptools/dist.py:765: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: BSD License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running install /usr/lib/python3.15/site-packages/setuptools/_distutils/cmd.py:90: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. Follow the current Python packaging guidelines when building Python RPM packages. This deprecation is overdue, please update your project and remove deprecated calls to avoid build errors in the future. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html and https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ for details. ******************************************************************************** !! self.initialize_options() running install_lib creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2 copying build/lib/django_tables2/__init__.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2 copying build/lib/django_tables2/config.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2 copying build/lib/django_tables2/data.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2 copying build/lib/django_tables2/paginators.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2 copying build/lib/django_tables2/rows.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2 copying build/lib/django_tables2/tables.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2 copying build/lib/django_tables2/utils.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2 copying build/lib/django_tables2/views.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2 creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/__init__.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/base.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/booleancolumn.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/checkboxcolumn.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/datecolumn.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/datetimecolumn.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/emailcolumn.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/filecolumn.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/jsoncolumn.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/linkcolumn.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/manytomanycolumn.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/templatecolumn.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/timecolumn.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/urlcolumn.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/export copying build/lib/django_tables2/export/__init__.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/export copying build/lib/django_tables2/export/export.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/export copying build/lib/django_tables2/export/views.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/export creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templatetags copying build/lib/django_tables2/templatetags/__init__.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templatetags copying build/lib/django_tables2/templatetags/django_tables2.py -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templatetags creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/cs creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/cs/LC_MESSAGES copying build/lib/django_tables2/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/cs/LC_MESSAGES copying build/lib/django_tables2/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/cs/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/de creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/de/LC_MESSAGES copying build/lib/django_tables2/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/de/LC_MESSAGES copying build/lib/django_tables2/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/de/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/el creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/el/LC_MESSAGES copying build/lib/django_tables2/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/el/LC_MESSAGES copying build/lib/django_tables2/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/el/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/en creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/en/LC_MESSAGES copying build/lib/django_tables2/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/en/LC_MESSAGES copying build/lib/django_tables2/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/en/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/es creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/es/LC_MESSAGES copying build/lib/django_tables2/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/es/LC_MESSAGES copying build/lib/django_tables2/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/es/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/fr creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/fr/LC_MESSAGES copying build/lib/django_tables2/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/fr/LC_MESSAGES copying build/lib/django_tables2/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/fr/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/hu creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/hu/LC_MESSAGES copying build/lib/django_tables2/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/hu/LC_MESSAGES copying build/lib/django_tables2/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/hu/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/it creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/it/LC_MESSAGES copying build/lib/django_tables2/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/it/LC_MESSAGES copying build/lib/django_tables2/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/it/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/lt creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/lt/LC_MESSAGES copying build/lib/django_tables2/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/lt/LC_MESSAGES copying build/lib/django_tables2/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/lt/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/nb creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/nb/LC_MESSAGES copying build/lib/django_tables2/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/nb/LC_MESSAGES copying build/lib/django_tables2/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/nb/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/nl creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/nl/LC_MESSAGES copying build/lib/django_tables2/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/nl/LC_MESSAGES copying build/lib/django_tables2/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/nl/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/pl creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/pl/LC_MESSAGES copying build/lib/django_tables2/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/pl/LC_MESSAGES copying build/lib/django_tables2/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/pl/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/pt_BR creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/pt_BR/LC_MESSAGES copying build/lib/django_tables2/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/pt_BR/LC_MESSAGES copying build/lib/django_tables2/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/pt_PT creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/pt_PT/LC_MESSAGES copying build/lib/django_tables2/locale/pt_PT/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/pt_PT/LC_MESSAGES copying build/lib/django_tables2/locale/pt_PT/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/pt_PT/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/ru creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/ru/LC_MESSAGES copying build/lib/django_tables2/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/ru/LC_MESSAGES copying build/lib/django_tables2/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/ru/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/sv creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/sv/LC_MESSAGES copying build/lib/django_tables2/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/sv/LC_MESSAGES copying build/lib/django_tables2/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/sv/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/uk creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/uk/LC_MESSAGES copying build/lib/django_tables2/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/uk/LC_MESSAGES copying build/lib/django_tables2/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/uk/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/zh_Hans creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/zh_Hans/LC_MESSAGES copying build/lib/django_tables2/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/zh_Hans/LC_MESSAGES copying build/lib/django_tables2/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2 copying build/lib/django_tables2/static/django_tables2/bootstrap.css -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2 creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes/paleblue creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes/paleblue/css copying build/lib/django_tables2/static/django_tables2/themes/paleblue/css/screen.css -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes/paleblue/css creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes/paleblue/img copying build/lib/django_tables2/static/django_tables2/themes/paleblue/img/arrow-active-down.png -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes/paleblue/img copying build/lib/django_tables2/static/django_tables2/themes/paleblue/img/arrow-active-up.png -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes/paleblue/img copying build/lib/django_tables2/static/django_tables2/themes/paleblue/img/arrow-inactive-down.png -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes/paleblue/img copying build/lib/django_tables2/static/django_tables2/themes/paleblue/img/arrow-inactive-up.png -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes/paleblue/img copying build/lib/django_tables2/static/django_tables2/themes/paleblue/img/false.gif -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes/paleblue/img copying build/lib/django_tables2/static/django_tables2/themes/paleblue/img/header-bg.png -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes/paleblue/img copying build/lib/django_tables2/static/django_tables2/themes/paleblue/img/missing.png -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes/paleblue/img copying build/lib/django_tables2/static/django_tables2/themes/paleblue/img/pagination-bg.gif -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes/paleblue/img copying build/lib/django_tables2/static/django_tables2/themes/paleblue/img/true.gif -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/static/django_tables2/themes/paleblue/img creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templates creating /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templates/django_tables2 copying build/lib/django_tables2/templates/django_tables2/bootstrap-responsive.html -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templates/django_tables2 copying build/lib/django_tables2/templates/django_tables2/bootstrap.html -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templates/django_tables2 copying build/lib/django_tables2/templates/django_tables2/bootstrap4.html -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templates/django_tables2 copying build/lib/django_tables2/templates/django_tables2/semantic.html -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templates/django_tables2 copying build/lib/django_tables2/templates/django_tables2/table.html -> /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templates/django_tables2 byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/__init__.py to __init__.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/config.py to config.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/data.py to data.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/paginators.py to paginators.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/rows.py to rows.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/tables.py to tables.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/utils.py to utils.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/views.py to views.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__init__.py to __init__.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/base.py to base.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/booleancolumn.py to booleancolumn.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/checkboxcolumn.py to checkboxcolumn.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/datecolumn.py to datecolumn.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/datetimecolumn.py to datetimecolumn.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/emailcolumn.py to emailcolumn.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/filecolumn.py to filecolumn.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/jsoncolumn.py to jsoncolumn.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/linkcolumn.py to linkcolumn.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/manytomanycolumn.py to manytomanycolumn.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/templatecolumn.py to templatecolumn.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/timecolumn.py to timecolumn.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/urlcolumn.py to urlcolumn.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/export/__init__.py to __init__.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/export/export.py to export.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/export/views.py to views.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templatetags/__init__.py to __init__.cpython-315.pyc byte-compiling /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templatetags/django_tables2.py to django_tables2.cpython-315.pyc writing byte-compilation script '/tmp/tmpuaa97bar.py' /usr/bin/python3 /tmp/tmpuaa97bar.py removing /tmp/tmpuaa97bar.py running install_egg_info running egg_info writing django_tables2.egg-info/PKG-INFO writing dependency_links to django_tables2.egg-info/dependency_links.txt writing requirements to django_tables2.egg-info/requires.txt writing top-level names to django_tables2.egg-info/top_level.txt reading manifest file 'django_tables2.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' warning: no previously-included files found matching 'docs/pages/CHANGELOG.md' warning: no previously-included files matching '*' found under directory 'docs/_build' adding license file 'LICENSE' writing manifest file 'django_tables2.egg-info/SOURCES.txt' Copying django_tables2.egg-info to /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2-2.4.0-py3.15.egg-info running install_scripts + rm -rfv /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/bin/__pycache__ + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-ldconfig + COMPRESS='gzip -9 -n' + COMPRESS_EXT=.gz + /usr/lib/rpm/brp-compress + /usr/lib/rpm/brp-strip /usr/bin/strip + /usr/lib/rpm/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/redhat/brp-strip-lto /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/redhat/brp-mangle-shebangs + /usr/lib/rpm/brp-remove-la-files + /usr/lib/rpm/redhat/brp-python-rpm-in-distinfo + env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j8 Bytecompiling .py files below /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15 using python3.15 + /usr/lib/rpm/redhat/brp-python-hardlink + /usr/bin/add-det --brp -j8 /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/__init__.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/datecolumn.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/booleancolumn.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/datetimecolumn.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/checkboxcolumn.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/emailcolumn.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/jsoncolumn.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/filecolumn.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/linkcolumn.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/templatecolumn.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/manytomanycolumn.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/timecolumn.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/urlcolumn.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/export/__pycache__/__init__.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templatetags/__pycache__/__init__.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/export/__pycache__/views.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/export/__pycache__/export.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/columns/__pycache__/base.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/templatetags/__pycache__/django_tables2.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/__pycache__/__init__.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/__pycache__/config.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/__pycache__/paginators.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/__pycache__/data.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/__pycache__/rows.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/__pycache__/tables.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/__pycache__/views.cpython-315.pyc: rewriting with normalized contents /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/lib/python3.15/site-packages/django_tables2/__pycache__/utils.cpython-315.pyc: rewriting with normalized contents Scanned 59 directories and 138 files, processed 32 inodes, 27 modified (0 replaced + 27 rewritten), 0 unsupported format, 0 errors + /usr/bin/linkdupes --brp /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr Scanned 58 directories and 138 files, considered 138 files, read 0 files, linked 0 files, 0 errors sum of sizes of linked files: 0 bytes Processing files: python3-django-tables2-2.4.0-21.fc45.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.WDDzBZ + umask 022 + cd /builddir/build/BUILD/python-django-tables2-2.4.0-build + cd django-tables2-2.4.0 + DOCDIR=/builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/share/doc/python3-django-tables2 + export LC_ALL=C.UTF-8 + LC_ALL=C.UTF-8 + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/share/doc/python3-django-tables2 + cp -pr /builddir/build/BUILD/python-django-tables2-2.4.0-build/django-tables2-2.4.0/README.md /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/share/doc/python3-django-tables2 + cp -pr /builddir/build/BUILD/python-django-tables2-2.4.0-build/django-tables2-2.4.0/CHANGELOG.md /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/share/doc/python3-django-tables2 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.3mfvg3 + umask 022 + cd /builddir/build/BUILD/python-django-tables2-2.4.0-build + cd django-tables2-2.4.0 + LICENSEDIR=/builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/share/licenses/python3-django-tables2 + export LC_ALL=C.UTF-8 + LC_ALL=C.UTF-8 + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/share/licenses/python3-django-tables2 + cp -pr /builddir/build/BUILD/python-django-tables2-2.4.0-build/django-tables2-2.4.0/LICENSE /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT/usr/share/licenses/python3-django-tables2 + RPM_EC=0 ++ jobs -p + exit 0 Provides: python-django-tables2 = 2.4.0-21.fc45 python3-django-tables2 = 2.4.0-21.fc45 python3.15-django-tables2 = 2.4.0-21.fc45 python3.15dist(django-tables2) = 2.4 python3dist(django-tables2) = 2.4 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.15 python3.15dist(django) >= 1.11 Obsoletes: python-django-tables2 < 1.2.3-5 python-django-tables2 < 2.4.0-21.fc45 python2-django-tables2 < 1.2.3-5 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILD/python-django-tables2-2.4.0-build/BUILDROOT Wrote: /builddir/build/RPMS/python3-django-tables2-2.4.0-21.fc45.noarch.rpm RPM build warnings: The %py3_build macro is deprecated and will likely stop working in Fedora 45. See the current Python packaging guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ The %py3_install macro is deprecated and will likely stop working in Fedora 45. See the current Python packaging guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ Child return code was: 0