Mock Version: 4.1 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/python-django-tables2.spec'], chrootPath='/var/lib/mock/fedora-rawhide-x86_64-1686145355.514905/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=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.bbt26zpz:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueprintOutput=True) Using nspawn with args ['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.bbt26zpz:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--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', 'b65e90f85823435d915c002fa550b036', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1686145355.514905/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.bbt26zpz:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--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 --target x86_64 --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: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1674172800 Wrote: /builddir/build/SRPMS/python-django-tables2-2.4.0-6.fc39.src.rpm Child return code was: 0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --target x86_64 --nodeps /builddir/build/SPECS/python-django-tables2.spec'], chrootPath='/var/lib/mock/fedora-rawhide-x86_64-1686145355.514905/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=0uid=1000gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.bbt26zpz:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueprintOutput=True) Using nspawn with args ['--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.bbt26zpz:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--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', 'a55add5a5d6e46318573a0b4f76c599e', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1686145355.514905/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.bbt26zpz:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--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 --target x86_64 --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: x86_64 Building for target x86_64 setting SOURCE_DATE_EPOCH=1674172800 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.PNVbGP + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf django-tables2-2.4.0 + /usr/lib/rpm/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/mkdir -p SPECPARTS + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + rm -vr django_tables2.egg-info/ removed 'django_tables2.egg-info/top_level.txt' removed 'django_tables2.egg-info/requires.txt' removed 'django_tables2.egg-info/dependency_links.txt' removed 'django_tables2.egg-info/SOURCES.txt' removed 'django_tables2.egg-info/PKG-INFO' removed directory 'django_tables2.egg-info/' + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.ecJXXG + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + 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 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -sP' running build running build_py creating build creating build/lib creating build/lib/django_tables2 copying django_tables2/views.py -> build/lib/django_tables2 copying django_tables2/utils.py -> build/lib/django_tables2 copying django_tables2/tables.py -> build/lib/django_tables2 copying django_tables2/rows.py -> build/lib/django_tables2 copying django_tables2/paginators.py -> build/lib/django_tables2 copying django_tables2/data.py -> build/lib/django_tables2 copying django_tables2/config.py -> build/lib/django_tables2 copying django_tables2/__init__.py -> build/lib/django_tables2 creating build/lib/django_tables2/templatetags copying django_tables2/templatetags/django_tables2.py -> build/lib/django_tables2/templatetags copying django_tables2/templatetags/__init__.py -> build/lib/django_tables2/templatetags creating build/lib/django_tables2/export copying django_tables2/export/views.py -> build/lib/django_tables2/export copying django_tables2/export/export.py -> build/lib/django_tables2/export copying django_tables2/export/__init__.py -> build/lib/django_tables2/export creating build/lib/django_tables2/columns copying django_tables2/columns/urlcolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/timecolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/templatecolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/manytomanycolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/linkcolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/jsoncolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/filecolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/emailcolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/datetimecolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/datecolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/checkboxcolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/booleancolumn.py -> build/lib/django_tables2/columns copying django_tables2/columns/base.py -> build/lib/django_tables2/columns copying django_tables2/columns/__init__.py -> build/lib/django_tables2/columns 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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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) creating build/lib/django_tables2/locale creating build/lib/django_tables2/locale/cs 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 creating build/lib/django_tables2/static/django_tables2/themes/paleblue 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 /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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.12/site-packages/setuptools/command/build_py.py:201: _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) 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.c45w2H + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64 ++ dirname /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64 + CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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 -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -I/usr/lib64/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cforce-frame-pointers=yes -Clink-arg=-Wl,-z,relro -Clink-arg=-Wl,-z,now -Clink-arg=-specs=/usr/lib/rpm/redhat/redhat-package-notes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + 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 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -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-annobin-cc1 -Wl,--build-id=sha1 -specs=/usr/lib/rpm/redhat/redhat-package-notes ' + /usr/bin/python3 setup.py install -O1 --skip-build --root /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64 --prefix /usr running install /usr/lib/python3.12/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer, pypa/build or other standards-based tools. Follow the current Python packaging guidelines when building Python RPM packages. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html and https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ for details. ******************************************************************************** !! self.initialize_options() running install_lib creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12 creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2 creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/templates creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/templates/django_tables2 copying build/lib/django_tables2/templates/django_tables2/table.html -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/templates/django_tables2 copying build/lib/django_tables2/templates/django_tables2/semantic.html -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/templates/django_tables2 copying build/lib/django_tables2/templates/django_tables2/bootstrap4.html -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/templates/django_tables2 copying build/lib/django_tables2/templates/django_tables2/bootstrap.html -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/templates/django_tables2 copying build/lib/django_tables2/templates/django_tables2/bootstrap-responsive.html -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/templates/django_tables2 creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/static creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/static/django_tables2 creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/static/django_tables2/themes creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/static/django_tables2/themes/paleblue creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/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/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/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/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/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/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/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/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/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/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/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/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/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/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/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/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/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/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/static/django_tables2/themes/paleblue/img creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/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/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/static/django_tables2/themes/paleblue/css copying build/lib/django_tables2/static/django_tables2/bootstrap.css -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/static/django_tables2 creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/zh_Hans creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/zh_Hans/LC_MESSAGES copying build/lib/django_tables2/locale/zh_Hans/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/zh_Hans/LC_MESSAGES copying build/lib/django_tables2/locale/zh_Hans/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/zh_Hans/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/uk creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/uk/LC_MESSAGES copying build/lib/django_tables2/locale/uk/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/uk/LC_MESSAGES copying build/lib/django_tables2/locale/uk/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/uk/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/sv creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/sv/LC_MESSAGES copying build/lib/django_tables2/locale/sv/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/sv/LC_MESSAGES copying build/lib/django_tables2/locale/sv/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/sv/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/ru creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/ru/LC_MESSAGES copying build/lib/django_tables2/locale/ru/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/ru/LC_MESSAGES copying build/lib/django_tables2/locale/ru/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/ru/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/pt_PT creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/pt_PT/LC_MESSAGES copying build/lib/django_tables2/locale/pt_PT/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/pt_PT/LC_MESSAGES copying build/lib/django_tables2/locale/pt_PT/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/pt_PT/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/pt_BR creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/pt_BR/LC_MESSAGES copying build/lib/django_tables2/locale/pt_BR/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/pt_BR/LC_MESSAGES copying build/lib/django_tables2/locale/pt_BR/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/pt_BR/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/pl creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/pl/LC_MESSAGES copying build/lib/django_tables2/locale/pl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/pl/LC_MESSAGES copying build/lib/django_tables2/locale/pl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/pl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/nl creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/nl/LC_MESSAGES copying build/lib/django_tables2/locale/nl/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/nl/LC_MESSAGES copying build/lib/django_tables2/locale/nl/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/nl/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/nb creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/nb/LC_MESSAGES copying build/lib/django_tables2/locale/nb/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/nb/LC_MESSAGES copying build/lib/django_tables2/locale/nb/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/nb/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/lt creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/lt/LC_MESSAGES copying build/lib/django_tables2/locale/lt/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/lt/LC_MESSAGES copying build/lib/django_tables2/locale/lt/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/lt/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/it creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/it/LC_MESSAGES copying build/lib/django_tables2/locale/it/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/it/LC_MESSAGES copying build/lib/django_tables2/locale/it/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/it/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/hu creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/hu/LC_MESSAGES copying build/lib/django_tables2/locale/hu/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/hu/LC_MESSAGES copying build/lib/django_tables2/locale/hu/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/hu/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/fr creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/fr/LC_MESSAGES copying build/lib/django_tables2/locale/fr/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/fr/LC_MESSAGES copying build/lib/django_tables2/locale/fr/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/fr/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/es creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/es/LC_MESSAGES copying build/lib/django_tables2/locale/es/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/es/LC_MESSAGES copying build/lib/django_tables2/locale/es/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/es/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/en creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/en/LC_MESSAGES copying build/lib/django_tables2/locale/en/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/en/LC_MESSAGES copying build/lib/django_tables2/locale/en/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/en/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/el creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/el/LC_MESSAGES copying build/lib/django_tables2/locale/el/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/el/LC_MESSAGES copying build/lib/django_tables2/locale/el/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/el/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/de creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/de/LC_MESSAGES copying build/lib/django_tables2/locale/de/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/de/LC_MESSAGES copying build/lib/django_tables2/locale/de/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/de/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/cs creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/cs/LC_MESSAGES copying build/lib/django_tables2/locale/cs/LC_MESSAGES/django.po -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/cs/LC_MESSAGES copying build/lib/django_tables2/locale/cs/LC_MESSAGES/django.mo -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/locale/cs/LC_MESSAGES creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/__init__.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/base.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/booleancolumn.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/checkboxcolumn.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/datecolumn.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/datetimecolumn.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/emailcolumn.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/filecolumn.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/jsoncolumn.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/linkcolumn.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/manytomanycolumn.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/templatecolumn.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/timecolumn.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns copying build/lib/django_tables2/columns/urlcolumn.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/export copying build/lib/django_tables2/export/__init__.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/export copying build/lib/django_tables2/export/export.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/export copying build/lib/django_tables2/export/views.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/export creating /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/templatetags copying build/lib/django_tables2/templatetags/__init__.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/templatetags copying build/lib/django_tables2/templatetags/django_tables2.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/templatetags copying build/lib/django_tables2/__init__.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2 copying build/lib/django_tables2/config.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2 copying build/lib/django_tables2/data.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2 copying build/lib/django_tables2/paginators.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2 copying build/lib/django_tables2/rows.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2 copying build/lib/django_tables2/tables.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2 copying build/lib/django_tables2/utils.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2 copying build/lib/django_tables2/views.py -> /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2 byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/__init__.py to __init__.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/base.py to base.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/booleancolumn.py to booleancolumn.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/checkboxcolumn.py to checkboxcolumn.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/datecolumn.py to datecolumn.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/datetimecolumn.py to datetimecolumn.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/emailcolumn.py to emailcolumn.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/filecolumn.py to filecolumn.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/jsoncolumn.py to jsoncolumn.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/linkcolumn.py to linkcolumn.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/manytomanycolumn.py to manytomanycolumn.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/templatecolumn.py to templatecolumn.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/timecolumn.py to timecolumn.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/columns/urlcolumn.py to urlcolumn.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/export/__init__.py to __init__.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/export/export.py to export.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/export/views.py to views.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/templatetags/__init__.py to __init__.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/templatetags/django_tables2.py to django_tables2.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/__init__.py to __init__.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/config.py to config.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/data.py to data.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/paginators.py to paginators.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/rows.py to rows.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/tables.py to tables.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/utils.py to utils.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2/views.py to views.cpython-312.pyc writing byte-compilation script '/tmp/tmpbme0ut7v.py' /usr/bin/python3 /tmp/tmpbme0ut7v.py removing /tmp/tmpbme0ut7v.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/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12/site-packages/django_tables2-2.4.0-py3.12.egg-info running install_scripts + rm -rfv /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/bin/__pycache__ + /usr/bin/find-debuginfo -j2 --strict-build-id -m -i --build-id-seed 2.4.0-6.fc39 --unique-debug-suffix -2.4.0-6.fc39.x86_64 --unique-debug-src-base python-django-tables2-2.4.0-6.fc39.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 -S debugsourcefiles.list /builddir/build/BUILD/django-tables2-2.4.0 find: 'debug': No such file or directory + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-ldconfig + /usr/lib/rpm/brp-compress + /usr/lib/rpm/redhat/brp-strip-lto /usr/bin/strip + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/redhat/brp-mangle-shebangs + /usr/lib/rpm/brp-remove-la-files + env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j2 Bytecompiling .py files below /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/lib/python3.12 using python3.12 + /usr/lib/rpm/redhat/brp-python-hardlink Processing files: python3-django-tables2-2.4.0-6.fc39.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.IDvUPZ + umask 022 + cd /builddir/build/BUILD + cd django-tables2-2.4.0 + DOCDIR=/builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/share/doc/python3-django-tables2 + export LC_ALL=C + LC_ALL=C + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/share/doc/python3-django-tables2 + cp -pr /builddir/build/BUILD/django-tables2-2.4.0/README.md /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/share/doc/python3-django-tables2 + cp -pr /builddir/build/BUILD/django-tables2-2.4.0/CHANGELOG.md /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/share/doc/python3-django-tables2 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.t7EFgU + umask 022 + cd /builddir/build/BUILD + cd django-tables2-2.4.0 + LICENSEDIR=/builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/share/licenses/python3-django-tables2 + export LC_ALL=C + LC_ALL=C + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/share/licenses/python3-django-tables2 + cp -pr /builddir/build/BUILD/django-tables2-2.4.0/LICENSE /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64/usr/share/licenses/python3-django-tables2 + RPM_EC=0 ++ jobs -p + exit 0 Provides: python-django-tables2 = 2.4.0-6.fc39 python3-django-tables2 = 2.4.0-6.fc39 python3.12-django-tables2 = 2.4.0-6.fc39 python3.12dist(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.12 python3.12dist(django) >= 1.11 Obsoletes: python-django-tables2 < 1.2.3-5 python-django-tables2 < 2.4.0-6.fc39 python2-django-tables2 < 1.2.3-5 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64 Wrote: /builddir/build/RPMS/python3-django-tables2-2.4.0-6.fc39.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.N0cmtm + umask 022 + cd /builddir/build/BUILD + cd django-tables2-2.4.0 + /usr/bin/rm -rf /builddir/build/BUILDROOT/python-django-tables2-2.4.0-6.fc39.x86_64 + RPM_EC=0 ++ jobs -p + exit 0 Executing(rmbuild): /bin/sh -e /var/tmp/rpm-tmp.3kENjt + umask 022 + cd /builddir/build/BUILD + rm -rf django-tables2-2.4.0 django-tables2-2.4.0.gemspec + RPM_EC=0 ++ jobs -p + exit 0 Child return code was: 0