Mock Version: 4.1 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --target x86_64 --nodeps /builddir/build/SPECS/python-django-health-check.spec'], chrootPath='/var/lib/mock/fedora-rawhide-x86_64-1686643701.742422/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.hfqfu04u:/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.hfqfu04u:/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', 'eae9bcb24e564b608d22b1226d8eecc8', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1686643701.742422/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.hfqfu04u:/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-health-check.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-health-check-3.16.5-4.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-health-check.spec'], chrootPath='/var/lib/mock/fedora-rawhide-x86_64-1686643701.742422/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.hfqfu04u:/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.hfqfu04u:/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', '52402bae434b43b89f484aa89832aa0c', '-D', '/var/lib/mock/fedora-rawhide-x86_64-1686643701.742422/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--rlimit=RLIMIT_NOFILE=10240', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.hfqfu04u:/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-health-check.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.vT1DXS + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf django-health-check-3.16.5 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/django-health-check-3.16.5.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd django-health-check-3.16.5 + /usr/bin/mkdir -p SPECPARTS + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.0bSJCv + 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-health-check-3.16.5 + 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' /usr/lib/python3.11/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) /usr/lib/python3.11/site-packages/setuptools/__init__.py:84: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! ******************************************************************************** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. ******************************************************************************** !! dist.fetch_build_eggs(dist.setup_requires) WARNING: The wheel package is not available. /usr/lib/python3.11/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) running build running build_py creating build creating build/lib creating build/lib/health_check copying health_check/views.py -> build/lib/health_check copying health_check/urls.py -> build/lib/health_check copying health_check/plugins.py -> build/lib/health_check copying health_check/mixins.py -> build/lib/health_check copying health_check/exceptions.py -> build/lib/health_check copying health_check/conf.py -> build/lib/health_check copying health_check/backends.py -> build/lib/health_check copying health_check/__init__.py -> build/lib/health_check running egg_info writing django_health_check.egg-info/PKG-INFO writing dependency_links to django_health_check.egg-info/dependency_links.txt writing requirements to django_health_check.egg-info/requires.txt writing top-level names to django_health_check.egg-info/top_level.txt reading manifest file 'django_health_check.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'tests' no previously-included directories found matching 'docs' adding license file 'LICENSE' writing manifest file 'django_health_check.egg-info/SOURCES.txt' /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.cache' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.cache' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.cache' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.cache' to be distributed and are already explicitly excluding 'health_check.cache' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.contrib' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.contrib' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.contrib' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.contrib' to be distributed and are already explicitly excluding 'health_check.contrib' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.contrib.celery' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.contrib.celery' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.contrib.celery' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.contrib.celery' to be distributed and are already explicitly excluding 'health_check.contrib.celery' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.contrib.celery_ping' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.contrib.celery_ping' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.contrib.celery_ping' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.contrib.celery_ping' to be distributed and are already explicitly excluding 'health_check.contrib.celery_ping' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.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/health_check/cache copying health_check/cache/__init__.py -> build/lib/health_check/cache copying health_check/cache/apps.py -> build/lib/health_check/cache copying health_check/cache/backends.py -> build/lib/health_check/cache creating build/lib/health_check/contrib copying health_check/contrib/__init__.py -> build/lib/health_check/contrib creating build/lib/health_check/contrib/celery copying health_check/contrib/celery/__init__.py -> build/lib/health_check/contrib/celery copying health_check/contrib/celery/apps.py -> build/lib/health_check/contrib/celery copying health_check/contrib/celery/backends.py -> build/lib/health_check/contrib/celery copying health_check/contrib/celery/tasks.py -> build/lib/health_check/contrib/celery creating build/lib/health_check/contrib/celery_ping copying health_check/contrib/celery_ping/__init__.py -> build/lib/health_check/contrib/celery_ping copying health_check/contrib/celery_ping/apps.py -> build/lib/health_check/contrib/celery_ping copying health_check/contrib/celery_ping/backends.py -> build/lib/health_check/contrib/celery_ping creating build/lib/health_check/contrib/migrations copying health_check/contrib/migrations/__init__.py -> build/lib/health_check/contrib/migrations copying health_check/contrib/migrations/apps.py -> build/lib/health_check/contrib/migrations copying health_check/contrib/migrations/backends.py -> build/lib/health_check/contrib/migrations creating build/lib/health_check/contrib/psutil copying health_check/contrib/psutil/__init__.py -> build/lib/health_check/contrib/psutil copying health_check/contrib/psutil/apps.py -> build/lib/health_check/contrib/psutil copying health_check/contrib/psutil/backends.py -> build/lib/health_check/contrib/psutil creating build/lib/health_check/contrib/rabbitmq copying health_check/contrib/rabbitmq/__init__.py -> build/lib/health_check/contrib/rabbitmq copying health_check/contrib/rabbitmq/apps.py -> build/lib/health_check/contrib/rabbitmq copying health_check/contrib/rabbitmq/backends.py -> build/lib/health_check/contrib/rabbitmq creating build/lib/health_check/contrib/redis copying health_check/contrib/redis/__init__.py -> build/lib/health_check/contrib/redis /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.contrib.migrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.contrib.migrations' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.contrib.migrations' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.contrib.migrations' to be distributed and are already explicitly excluding 'health_check.contrib.migrations' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.contrib.psutil' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.contrib.psutil' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.contrib.psutil' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.contrib.psutil' to be distributed and are already explicitly excluding 'health_check.contrib.psutil' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.contrib.rabbitmq' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.contrib.rabbitmq' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.contrib.rabbitmq' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.contrib.rabbitmq' to be distributed and are already explicitly excluding 'health_check.contrib.rabbitmq' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.contrib.redis' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.contrib.redis' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.contrib.redis' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.contrib.redis' to be distributed and are already explicitly excluding 'health_check.contrib.redis' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.contrib.s3boto3_storage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.contrib.s3boto3_storage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.contrib.s3boto3_storage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.contrib.s3boto3_storage' to be distributed and are already explicitly excluding 'health_check.contrib.s3boto3_storage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.contrib.s3boto_storage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.contrib.s3boto_storage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.contrib.s3boto_storage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.contrib.s3boto_storage' to be distributed and are already explicitly excluding 'health_check.contrib.s3boto_storage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.db' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.db' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.db' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.db' to be distributed and are already explicitly excluding 'health_check.db' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.db.migrations' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.db.migrations' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.db.migrations' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.db.migrations' to be distributed and are already explicitly excluding 'health_check.db.migrations' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.management' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.management' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.management' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.management' to be distributed and are already explicitly excluding 'health_check.management' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.management.commands' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.management.commands' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.management.commands' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.management.commands' to be distributed and are already explicitly excluding 'health_check.management.commands' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.storage' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.storage' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.storage' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.storage' to be distributed and are already explicitly excluding 'health_check.storage' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'health_check.templates.health_check' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'health_check.templates.health_check' as an importable package[^1], but it is absent from setuptools' `packages` configuration. This leads to an ambiguous overall configuration. If you want to distribute this package, please make sure that 'health_check.templates.health_check' is explicitly added to the `packages` configuration field. Alternatively, you can also rely on setuptools' discovery methods (for example by using `find_namespace_packages(...)`/`find_namespace:` instead of `find_packages(...)`/`find:`). You can read more about "package discovery" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/package_discovery.html If you don't want 'health_check.templates.health_check' to be distributed and are already explicitly excluding 'health_check.templates.health_check' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) copying health_check/contrib/redis/apps.py -> build/lib/health_check/contrib/redis copying health_check/contrib/redis/backends.py -> build/lib/health_check/contrib/redis creating build/lib/health_check/contrib/s3boto3_storage copying health_check/contrib/s3boto3_storage/__init__.py -> build/lib/health_check/contrib/s3boto3_storage copying health_check/contrib/s3boto3_storage/apps.py -> build/lib/health_check/contrib/s3boto3_storage copying health_check/contrib/s3boto3_storage/backends.py -> build/lib/health_check/contrib/s3boto3_storage creating build/lib/health_check/contrib/s3boto_storage copying health_check/contrib/s3boto_storage/__init__.py -> build/lib/health_check/contrib/s3boto_storage copying health_check/contrib/s3boto_storage/apps.py -> build/lib/health_check/contrib/s3boto_storage copying health_check/contrib/s3boto_storage/backends.py -> build/lib/health_check/contrib/s3boto_storage creating build/lib/health_check/db copying health_check/db/__init__.py -> build/lib/health_check/db copying health_check/db/apps.py -> build/lib/health_check/db copying health_check/db/backends.py -> build/lib/health_check/db copying health_check/db/models.py -> build/lib/health_check/db creating build/lib/health_check/db/migrations copying health_check/db/migrations/0001_initial.py -> build/lib/health_check/db/migrations copying health_check/db/migrations/__init__.py -> build/lib/health_check/db/migrations creating build/lib/health_check/management copying health_check/management/__init__.py -> build/lib/health_check/management creating build/lib/health_check/management/commands copying health_check/management/commands/__init__.py -> build/lib/health_check/management/commands copying health_check/management/commands/health_check.py -> build/lib/health_check/management/commands creating build/lib/health_check/storage copying health_check/storage/__init__.py -> build/lib/health_check/storage copying health_check/storage/apps.py -> build/lib/health_check/storage copying health_check/storage/backends.py -> build/lib/health_check/storage creating build/lib/health_check/templates creating build/lib/health_check/templates/health_check copying health_check/templates/health_check/index.html -> build/lib/health_check/templates/health_check Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.J5zIh4 + RPM_EC=0 ++ jobs -p + exit 0 + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64 '!=' / ']' + rm -rf /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64 ++ dirname /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64 + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.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-health-check-3.16.5 + 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-health-check-3.16.5-4.fc39.x86_64 --prefix /usr /usr/lib/python3.11/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) /usr/lib/python3.11/site-packages/setuptools/__init__.py:84: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. !! ******************************************************************************** Requirements should be satisfied by a PEP 517 installer. If you are using pip, you can try `pip install --use-pep517`. ******************************************************************************** !! dist.fetch_build_eggs(dist.setup_requires) WARNING: The wheel package is not available. /usr/lib/python3.11/site-packages/setuptools/config/setupcfg.py:293: _DeprecatedConfig: Deprecated config in `setup.cfg` !! ******************************************************************************** The license_file parameter is deprecated, use license_files instead. By 2023-Oct-30, you need to update your project and remove deprecated calls or your builds will no longer be supported. See https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for details. ******************************************************************************** !! parsed = self.parsers.get(option_name, lambda x: x)(value) running install /usr/lib/python3.11/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-health-check-3.16.5-4.fc39.x86_64/usr creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11 creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/templates creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/templates/health_check copying build/lib/health_check/templates/health_check/index.html -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/templates/health_check creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/storage copying build/lib/health_check/storage/backends.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/storage copying build/lib/health_check/storage/apps.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/storage copying build/lib/health_check/storage/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/storage creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/management creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/management/commands copying build/lib/health_check/management/commands/health_check.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/management/commands copying build/lib/health_check/management/commands/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/management/commands copying build/lib/health_check/management/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/management creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db/migrations copying build/lib/health_check/db/migrations/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db/migrations copying build/lib/health_check/db/migrations/0001_initial.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db/migrations copying build/lib/health_check/db/models.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db copying build/lib/health_check/db/backends.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db copying build/lib/health_check/db/apps.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db copying build/lib/health_check/db/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto_storage copying build/lib/health_check/contrib/s3boto_storage/backends.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto_storage copying build/lib/health_check/contrib/s3boto_storage/apps.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto_storage copying build/lib/health_check/contrib/s3boto_storage/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto_storage creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto3_storage copying build/lib/health_check/contrib/s3boto3_storage/backends.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto3_storage copying build/lib/health_check/contrib/s3boto3_storage/apps.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto3_storage copying build/lib/health_check/contrib/s3boto3_storage/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto3_storage creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/redis copying build/lib/health_check/contrib/redis/backends.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/redis copying build/lib/health_check/contrib/redis/apps.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/redis copying build/lib/health_check/contrib/redis/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/redis creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/rabbitmq copying build/lib/health_check/contrib/rabbitmq/backends.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/rabbitmq copying build/lib/health_check/contrib/rabbitmq/apps.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/rabbitmq copying build/lib/health_check/contrib/rabbitmq/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/rabbitmq creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/psutil copying build/lib/health_check/contrib/psutil/backends.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/psutil copying build/lib/health_check/contrib/psutil/apps.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/psutil copying build/lib/health_check/contrib/psutil/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/psutil creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/migrations copying build/lib/health_check/contrib/migrations/backends.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/migrations copying build/lib/health_check/contrib/migrations/apps.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/migrations copying build/lib/health_check/contrib/migrations/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/migrations creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery_ping copying build/lib/health_check/contrib/celery_ping/backends.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery_ping copying build/lib/health_check/contrib/celery_ping/apps.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery_ping copying build/lib/health_check/contrib/celery_ping/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery_ping creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery copying build/lib/health_check/contrib/celery/tasks.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery copying build/lib/health_check/contrib/celery/backends.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery copying build/lib/health_check/contrib/celery/apps.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery copying build/lib/health_check/contrib/celery/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery copying build/lib/health_check/contrib/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib creating /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/cache copying build/lib/health_check/cache/backends.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/cache copying build/lib/health_check/cache/apps.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/cache copying build/lib/health_check/cache/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/cache copying build/lib/health_check/__init__.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check copying build/lib/health_check/backends.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check copying build/lib/health_check/conf.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check copying build/lib/health_check/exceptions.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check copying build/lib/health_check/mixins.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check copying build/lib/health_check/plugins.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check copying build/lib/health_check/urls.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check copying build/lib/health_check/views.py -> /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/storage/backends.py to backends.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/storage/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/storage/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/management/commands/health_check.py to health_check.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/management/commands/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/management/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db/migrations/0001_initial.py to 0001_initial.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db/models.py to models.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db/backends.py to backends.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/db/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto_storage/backends.py to backends.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto_storage/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto_storage/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto3_storage/backends.py to backends.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto3_storage/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/s3boto3_storage/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/redis/backends.py to backends.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/redis/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/redis/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/rabbitmq/backends.py to backends.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/rabbitmq/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/rabbitmq/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/psutil/backends.py to backends.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/psutil/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/psutil/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/migrations/backends.py to backends.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/migrations/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/migrations/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery_ping/backends.py to backends.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery_ping/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery_ping/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery/tasks.py to tasks.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery/backends.py to backends.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/celery/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/contrib/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/cache/backends.py to backends.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/cache/apps.py to apps.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/cache/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/__init__.py to __init__.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/backends.py to backends.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/conf.py to conf.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/exceptions.py to exceptions.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/mixins.py to mixins.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/plugins.py to plugins.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/urls.py to urls.cpython-311.pyc byte-compiling /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/health_check/views.py to views.cpython-311.pyc writing byte-compilation script '/tmp/tmpbe0mas7q.py' /usr/bin/python3 /tmp/tmpbe0mas7q.py removing /tmp/tmpbe0mas7q.py running install_egg_info running egg_info writing django_health_check.egg-info/PKG-INFO writing dependency_links to django_health_check.egg-info/dependency_links.txt writing requirements to django_health_check.egg-info/requires.txt writing top-level names to django_health_check.egg-info/top_level.txt reading manifest file 'django_health_check.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'tests' adding license file 'LICENSE' no previously-included directories found matching 'docs' writing manifest file 'django_health_check.egg-info/SOURCES.txt' Copying django_health_check.egg-info to /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11/site-packages/django_health_check-3.16.5-py3.11.egg-info running install_scripts + rm -rfv /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/bin/__pycache__ + /usr/bin/find-debuginfo -j2 --strict-build-id -m -i --build-id-seed 3.16.5-4.fc39 --unique-debug-suffix -3.16.5-4.fc39.x86_64 --unique-debug-src-base python-django-health-check-3.16.5-4.fc39.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 -S debugsourcefiles.list /builddir/build/BUILD/django-health-check-3.16.5 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-health-check-3.16.5-4.fc39.x86_64/usr/lib/python3.11 using python3.11 + /usr/lib/rpm/redhat/brp-python-hardlink Processing files: python3-django-health-check-3.16.5-4.fc39.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.t0xQcW + umask 022 + cd /builddir/build/BUILD + cd django-health-check-3.16.5 + DOCDIR=/builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/share/doc/python3-django-health-check + export LC_ALL=C + LC_ALL=C + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/share/doc/python3-django-health-check + cp -pr /builddir/build/BUILD/django-health-check-3.16.5/README.rst /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/share/doc/python3-django-health-check + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.AEXq94 + umask 022 + cd /builddir/build/BUILD + cd django-health-check-3.16.5 + LICENSEDIR=/builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/share/licenses/python3-django-health-check + export LC_ALL=C + LC_ALL=C + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/share/licenses/python3-django-health-check + cp -pr /builddir/build/BUILD/django-health-check-3.16.5/LICENSE /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/share/licenses/python3-django-health-check + RPM_EC=0 ++ jobs -p + exit 0 Provides: python-django-health-check = 3.16.5-4.fc39 python3-django-health-check = 3.16.5-4.fc39 python3.11-django-health-check = 3.16.5-4.fc39 python3.11dist(django-health-check) = 3.16.5 python3dist(django-health-check) = 3.16.5 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.11 python3.11dist(django) >= 2.2 Obsoletes: python-django-health-check < 3.16.5-4.fc39 Processing files: python-django-health-check-doc-3.16.5-4.fc39.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.s0Jajy + umask 022 + cd /builddir/build/BUILD + cd django-health-check-3.16.5 + DOCDIR=/builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/share/doc/python-django-health-check-doc + export LC_ALL=C + LC_ALL=C + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/share/doc/python-django-health-check-doc + cp -pr /builddir/build/BUILD/django-health-check-3.16.5/README.rst /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/share/doc/python-django-health-check-doc + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.Sy3O4e + umask 022 + cd /builddir/build/BUILD + cd django-health-check-3.16.5 + LICENSEDIR=/builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/share/licenses/python-django-health-check-doc + export LC_ALL=C + LC_ALL=C + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/share/licenses/python-django-health-check-doc + cp -pr /builddir/build/BUILD/django-health-check-3.16.5/LICENSE /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64/usr/share/licenses/python-django-health-check-doc + RPM_EC=0 ++ jobs -p + exit 0 Provides: python-django-health-check-doc = 3.16.5-4.fc39 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64 Wrote: /builddir/build/RPMS/python-django-health-check-doc-3.16.5-4.fc39.noarch.rpm Wrote: /builddir/build/RPMS/python3-django-health-check-3.16.5-4.fc39.noarch.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.EQjTBn + umask 022 + cd /builddir/build/BUILD + cd django-health-check-3.16.5 + /usr/bin/rm -rf /builddir/build/BUILDROOT/python-django-health-check-3.16.5-4.fc39.x86_64 + RPM_EC=0 ++ jobs -p + exit 0 Executing(rmbuild): /bin/sh -e /var/tmp/rpm-tmp.NH45SD + umask 022 + cd /builddir/build/BUILD + rm -rf django-health-check-3.16.5 django-health-check-3.16.5.gemspec + RPM_EC=0 ++ jobs -p + exit 0 Child return code was: 0