Mock Version: 5.5 Mock Version: 5.5 Mock Version: 5.5 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/cinch.spec'], chrootPath='/var/lib/mock/f41-build-27434-1005/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=864000uid=997gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.axph0e1i:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueprintOutput=False) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.axph0e1i:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', '93d1dea496a24cdfaf33074af2debca5', '-D', '/var/lib/mock/f41-build-27434-1005/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.axph0e1i:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bs --noclean --target noarch --nodeps /builddir/build/SPECS/cinch.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1705968000 Wrote: /builddir/build/SRPMS/cinch-1.4.0-18.fc41.src.rpm Child return code was: 0 ENTER ['do_with_status'](['bash', '--login', '-c', '/usr/bin/rpmbuild -bb --noclean --target noarch --nodeps /builddir/build/SPECS/cinch.spec'], chrootPath='/var/lib/mock/f41-build-27434-1005/root'env={'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8'}shell=Falselogger=timeout=864000uid=997gid=135user='mockbuild'nspawn_args=['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.axph0e1i:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11']unshare_net=TrueprintOutput=False) Using nspawn with args ['--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.axph0e1i:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11'] Executing command: ['/usr/bin/systemd-nspawn', '-q', '-M', 'b2614076af9e4858bc09e99718d56db7', '-D', '/var/lib/mock/f41-build-27434-1005/root', '-a', '-u', 'mockbuild', '--capability=cap_ipc_lock', '--bind=/tmp/mock-resolv.axph0e1i:/etc/resolv.conf', '--bind=/dev/btrfs-control', '--bind=/dev/mapper/control', '--bind=/dev/fuse', '--bind=/dev/loop-control', '--bind=/dev/loop0', '--bind=/dev/loop1', '--bind=/dev/loop2', '--bind=/dev/loop3', '--bind=/dev/loop4', '--bind=/dev/loop5', '--bind=/dev/loop6', '--bind=/dev/loop7', '--bind=/dev/loop8', '--bind=/dev/loop9', '--bind=/dev/loop10', '--bind=/dev/loop11', '--console=pipe', '--setenv=TERM=vt100', '--setenv=SHELL=/bin/bash', '--setenv=HOME=/builddir', '--setenv=HOSTNAME=mock', '--setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin', '--setenv=PROMPT_COMMAND=printf "\\033]0;\\007"', '--setenv=PS1= \\s-\\v\\$ ', '--setenv=LANG=C.UTF-8', '--resolv-conf=off', 'bash', '--login', '-c', '/usr/bin/rpmbuild -bb --noclean --target noarch --nodeps /builddir/build/SPECS/cinch.spec'] with env {'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOME': '/builddir', 'HOSTNAME': 'mock', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'PS1': ' \\s-\\v\\$ ', 'LANG': 'C.UTF-8', 'SYSTEMD_NSPAWN_TMPFS_TMP': '0', 'SYSTEMD_SECCOMP': '0'} and shell False Building target platforms: noarch Building for target noarch setting SOURCE_DATE_EPOCH=1705968000 Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.lMSLgf + umask 022 + cd /builddir/build/BUILD + cd /builddir/build/BUILD + rm -rf cinch-1.4.0 + /usr/lib/rpm/rpmuncompress -x /builddir/build/SOURCES/v1.4.0.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd cinch-1.4.0 + rm -rf /builddir/build/BUILD/cinch-1.4.0-SPECPARTS + /usr/bin/mkdir -p /builddir/build/BUILD/cinch-1.4.0-SPECPARTS + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + find . -name '*.sh' -exec chmod +x '{}' ';' + find . -name '*.py' -exec chmod -x '{}' ';' + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.Fp6IXU + umask 022 + cd /builddir/build/BUILD + CFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables -fno-omit-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables -fno-omit-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables -fno-omit-frame-pointer -I/usr/lib/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables -fno-omit-frame-pointer -I/usr/lib/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd cinch-1.4.0 + CFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables -fno-omit-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + /usr/bin/python3 setup.py build '--executable=/usr/bin/python3 -sP' running build running build_py creating build creating build/lib creating build/lib/tests copying tests/__init__.py -> build/lib/tests copying tests/test_cli.py -> build/lib/tests creating build/lib/cinch copying cinch/__init__.py -> build/lib/cinch creating build/lib/tests/ansible_lint_rules copying tests/ansible_lint_rules/NoFormattingInWhenRule.py -> build/lib/tests/ansible_lint_rules copying tests/ansible_lint_rules/__init__.py -> build/lib/tests/ansible_lint_rules creating build/lib/cinch/bin copying cinch/bin/wrappers.py -> build/lib/cinch/bin copying cinch/bin/__init__.py -> build/lib/cinch/bin copying cinch/bin/entry_point.py -> build/lib/cinch/bin running egg_info creating cinch.egg-info writing cinch.egg-info/PKG-INFO writing dependency_links to cinch.egg-info/dependency_links.txt writing entry points to cinch.egg-info/entry_points.txt writing requirements to cinch.egg-info/requires.txt writing top-level names to cinch.egg-info/top_level.txt writing manifest file 'cinch.egg-info/SOURCES.txt' reading manifest file 'cinch.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'cinch.egg-info/SOURCES.txt' /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.files' 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 'cinch.files' 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 'cinch.files' to be distributed and are already explicitly excluding 'cinch.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.group_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.group_vars' 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 'cinch.group_vars' 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 'cinch.group_vars' to be distributed and are already explicitly excluding 'cinch.group_vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.library' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.library' 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 'cinch.library' 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 'cinch.library' to be distributed and are already explicitly excluding 'cinch.library' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles' 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 'cinch.roles' 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 'cinch.roles' to be distributed and are already explicitly excluding 'cinch.roles' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.certificate_authority.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.certificate_authority.defaults' 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 'cinch.roles.certificate_authority.defaults' 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 'cinch.roles.certificate_authority.defaults' to be distributed and are already explicitly excluding 'cinch.roles.certificate_authority.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.certificate_authority.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.certificate_authority.handlers' 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 'cinch.roles.certificate_authority.handlers' 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 'cinch.roles.certificate_authority.handlers' to be distributed and are already explicitly excluding 'cinch.roles.certificate_authority.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.certificate_authority.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.certificate_authority.tasks' 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 'cinch.roles.certificate_authority.tasks' 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 'cinch.roles.certificate_authority.tasks' to be distributed and are already explicitly excluding 'cinch.roles.certificate_authority.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.check_ssh.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.check_ssh.defaults' 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 'cinch.roles.check_ssh.defaults' 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 'cinch.roles.check_ssh.defaults' to be distributed and are already explicitly excluding 'cinch.roles.check_ssh.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.check_ssh.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.check_ssh.tasks' 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 'cinch.roles.check_ssh.tasks' 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 'cinch.roles.check_ssh.tasks' to be distributed and are already explicitly excluding 'cinch.roles.check_ssh.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.dockerize.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.dockerize.defaults' 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 'cinch.roles.dockerize.defaults' 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 'cinch.roles.dockerize.defaults' to be distributed and are already explicitly excluding 'cinch.roles.dockerize.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.dockerize.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.dockerize.tasks' 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 'cinch.roles.dockerize.tasks' 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 'cinch.roles.dockerize.tasks' to be distributed and are already explicitly excluding 'cinch.roles.dockerize.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_common.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_common.defaults' 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 'cinch.roles.jenkins_common.defaults' 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 'cinch.roles.jenkins_common.defaults' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_common.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_common.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_common.handlers' 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 'cinch.roles.jenkins_common.handlers' 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 'cinch.roles.jenkins_common.handlers' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_common.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_common.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_common.tasks' 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 'cinch.roles.jenkins_common.tasks' 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 'cinch.roles.jenkins_common.tasks' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_common.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_common.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_common.vars' 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 'cinch.roles.jenkins_common.vars' 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 'cinch.roles.jenkins_common.vars' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_common.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_docker_slave.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_docker_slave.defaults' 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 'cinch.roles.jenkins_docker_slave.defaults' 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 'cinch.roles.jenkins_docker_slave.defaults' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_docker_slave.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_docker_slave.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_docker_slave.tasks' 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 'cinch.roles.jenkins_docker_slave.tasks' 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 'cinch.roles.jenkins_docker_slave.tasks' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_docker_slave.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_master.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_master.defaults' 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 'cinch.roles.jenkins_master.defaults' 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 'cinch.roles.jenkins_master.defaults' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_master.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_master.files' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_master.files' 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 'cinch.roles.jenkins_master.files' 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 'cinch.roles.jenkins_master.files' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_master.files' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_master.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_master.handlers' 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 'cinch.roles.jenkins_master.handlers' 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 'cinch.roles.jenkins_master.handlers' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_master.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_master.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_master.tasks' 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 'cinch.roles.jenkins_master.tasks' 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 'cinch.roles.jenkins_master.tasks' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_master.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_master.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_master.templates' 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 'cinch.roles.jenkins_master.templates' 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 'cinch.roles.jenkins_master.templates' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_master.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_master.templates.etc.nginx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_master.templates.etc.nginx' 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 'cinch.roles.jenkins_master.templates.etc.nginx' 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 'cinch.roles.jenkins_master.templates.etc.nginx' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_master.templates.etc.nginx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_master.vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_master.vars' 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 'cinch.roles.jenkins_master.vars' 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 'cinch.roles.jenkins_master.vars' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_master.vars' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_master_stop.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_master_stop.tasks' 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 'cinch.roles.jenkins_master_stop.tasks' 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 'cinch.roles.jenkins_master_stop.tasks' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_master_stop.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_slave.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_slave.defaults' 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 'cinch.roles.jenkins_slave.defaults' 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 'cinch.roles.jenkins_slave.defaults' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_slave.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_slave.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_slave.handlers' 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 'cinch.roles.jenkins_slave.handlers' 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 'cinch.roles.jenkins_slave.handlers' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_slave.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_slave.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_slave.tasks' 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 'cinch.roles.jenkins_slave.tasks' 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 'cinch.roles.jenkins_slave.tasks' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_slave.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_slave.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_slave.templates' 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 'cinch.roles.jenkins_slave.templates' 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 'cinch.roles.jenkins_slave.templates' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_slave.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_slave_container_wrapup.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_slave_container_wrapup.defaults' 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 'cinch.roles.jenkins_slave_container_wrapup.defaults' 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 'cinch.roles.jenkins_slave_container_wrapup.defaults' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_slave_container_wrapup.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_slave_container_wrapup.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_slave_container_wrapup.tasks' 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 'cinch.roles.jenkins_slave_container_wrapup.tasks' 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 'cinch.roles.jenkins_slave_container_wrapup.tasks' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_slave_container_wrapup.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_slave_container_wrapup.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_slave_container_wrapup.templates' 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 'cinch.roles.jenkins_slave_container_wrapup.templates' 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 'cinch.roles.jenkins_slave_container_wrapup.templates' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_slave_container_wrapup.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.jenkins_slave_teardown.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.jenkins_slave_teardown.tasks' 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 'cinch.roles.jenkins_slave_teardown.tasks' 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 'cinch.roles.jenkins_slave_teardown.tasks' to be distributed and are already explicitly excluding 'cinch.roles.jenkins_slave_teardown.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.nginx.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.nginx.defaults' 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 'cinch.roles.nginx.defaults' 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 'cinch.roles.nginx.defaults' to be distributed and are already explicitly excluding 'cinch.roles.nginx.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.nginx.files.etc' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.nginx.files.etc' 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 'cinch.roles.nginx.files.etc' 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 'cinch.roles.nginx.files.etc' to be distributed and are already explicitly excluding 'cinch.roles.nginx.files.etc' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.nginx.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.nginx.handlers' 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 'cinch.roles.nginx.handlers' 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 'cinch.roles.nginx.handlers' to be distributed and are already explicitly excluding 'cinch.roles.nginx.handlers' 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 cinch/site.yml -> build/lib/cinch copying cinch/teardown.yml -> build/lib/cinch creating build/lib/cinch/files creating build/lib/cinch/files/jenkins-plugin-lists copying cinch/files/jenkins-plugin-lists/README -> build/lib/cinch/files/jenkins-plugin-lists copying cinch/files/jenkins-plugin-lists/default-test.txt -> build/lib/cinch/files/jenkins-plugin-lists copying cinch/files/jenkins-plugin-lists/default.txt -> build/lib/cinch/files/jenkins-plugin-lists copying cinch/files/jenkins-plugin-lists/optional-test.txt -> build/lib/cinch/files/jenkins-plugin-lists copying cinch/files/jenkins-plugin-lists/optional.txt -> build/lib/cinch/files/jenkins-plugin-lists creating build/lib/cinch/group_vars copying cinch/group_vars/all -> build/lib/cinch/group_vars copying cinch/group_vars/cent6 -> build/lib/cinch/group_vars copying cinch/group_vars/cent7 -> build/lib/cinch/group_vars copying cinch/group_vars/fedora -> build/lib/cinch/group_vars copying cinch/group_vars/jenkins_docker_slave -> build/lib/cinch/group_vars copying cinch/group_vars/jenkins_master -> build/lib/cinch/group_vars copying cinch/group_vars/jenkins_slave -> build/lib/cinch/group_vars copying cinch/group_vars/rhel6 -> build/lib/cinch/group_vars copying cinch/group_vars/rhel7 -> build/lib/cinch/group_vars copying cinch/group_vars/rhel8 -> build/lib/cinch/group_vars creating build/lib/cinch/library copying cinch/library/jenkins_cli_user.py -> build/lib/cinch/library copying cinch/library/jenkins_script.py -> build/lib/cinch/library copying cinch/library/jenkins_update_center.py -> build/lib/cinch/library copying cinch/library/jenkins_user_api.py -> build/lib/cinch/library copying cinch/library/line_match.py -> build/lib/cinch/library creating build/lib/cinch/roles creating build/lib/cinch/roles/beaker-client creating build/lib/cinch/roles/beaker-client/defaults copying cinch/roles/beaker-client/defaults/main.yml -> build/lib/cinch/roles/beaker-client/defaults creating build/lib/cinch/roles/beaker-client/tasks copying cinch/roles/beaker-client/tasks/main.yml -> build/lib/cinch/roles/beaker-client/tasks creating build/lib/cinch/roles/beaker-client/templates creating build/lib/cinch/roles/beaker-client/templates/etc creating build/lib/cinch/roles/beaker-client/templates/etc/beaker copying cinch/roles/beaker-client/templates/etc/beaker/client.conf -> build/lib/cinch/roles/beaker-client/templates/etc/beaker creating build/lib/cinch/roles/certificate_authority creating build/lib/cinch/roles/certificate_authority/defaults copying cinch/roles/certificate_authority/defaults/main.yml -> build/lib/cinch/roles/certificate_authority/defaults creating build/lib/cinch/roles/certificate_authority/handlers copying cinch/roles/certificate_authority/handlers/main.yml -> build/lib/cinch/roles/certificate_authority/handlers creating build/lib/cinch/roles/certificate_authority/tasks copying cinch/roles/certificate_authority/tasks/main.yml -> build/lib/cinch/roles/certificate_authority/tasks creating build/lib/cinch/roles/check_ssh creating build/lib/cinch/roles/check_ssh/defaults copying cinch/roles/check_ssh/defaults/main.yml -> build/lib/cinch/roles/check_ssh/defaults creating build/lib/cinch/roles/check_ssh/tasks copying cinch/roles/check_ssh/tasks/main.yml -> build/lib/cinch/roles/check_ssh/tasks creating build/lib/cinch/roles/dockerize creating build/lib/cinch/roles/dockerize/defaults copying cinch/roles/dockerize/defaults/main.yml -> build/lib/cinch/roles/dockerize/defaults creating build/lib/cinch/roles/dockerize/tasks copying cinch/roles/dockerize/tasks/main.yml -> build/lib/cinch/roles/dockerize/tasks creating build/lib/cinch/roles/jenkins_common creating build/lib/cinch/roles/jenkins_common/defaults copying cinch/roles/jenkins_common/defaults/main.yml -> build/lib/cinch/roles/jenkins_common/defaults creating build/lib/cinch/roles/jenkins_common/handlers copying cinch/roles/jenkins_common/handlers/main.yml -> build/lib/cinch/roles/jenkins_common/handlers creating build/lib/cinch/roles/jenkins_common/tasks copying cinch/roles/jenkins_common/tasks/main.yml -> build/lib/cinch/roles/jenkins_common/tasks creating build/lib/cinch/roles/jenkins_common/vars copying cinch/roles/jenkins_common/vars/main.yml -> build/lib/cinch/roles/jenkins_common/vars creating build/lib/cinch/roles/jenkins_docker_slave creating build/lib/cinch/roles/jenkins_docker_slave/defaults copying cinch/roles/jenkins_docker_slave/defaults/main.yml -> build/lib/cinch/roles/jenkins_docker_slave/defaults creating build/lib/cinch/roles/jenkins_docker_slave/tasks copying cinch/roles/jenkins_docker_slave/tasks/main.yml -> build/lib/cinch/roles/jenkins_docker_slave/tasks creating build/lib/cinch/roles/jenkins_master creating build/lib/cinch/roles/jenkins_master/defaults copying cinch/roles/jenkins_master/defaults/main.yml -> build/lib/cinch/roles/jenkins_master/defaults creating build/lib/cinch/roles/jenkins_master/files copying cinch/roles/jenkins_master/files/mass_disable.groovy -> build/lib/cinch/roles/jenkins_master/files copying cinch/roles/jenkins_master/files/set_env.groovy -> build/lib/cinch/roles/jenkins_master/files creating build/lib/cinch/roles/jenkins_master/handlers copying cinch/roles/jenkins_master/handlers/main.yml -> build/lib/cinch/roles/jenkins_master/handlers creating build/lib/cinch/roles/jenkins_master/tasks copying cinch/roles/jenkins_master/tasks/configure.yml -> build/lib/cinch/roles/jenkins_master/tasks copying cinch/roles/jenkins_master/tasks/ensure_up.yml -> build/lib/cinch/roles/jenkins_master/tasks copying cinch/roles/jenkins_master/tasks/firewalld.yml -> build/lib/cinch/roles/jenkins_master/tasks copying cinch/roles/jenkins_master/tasks/install.yml -> build/lib/cinch/roles/jenkins_master/tasks copying cinch/roles/jenkins_master/tasks/main.yml -> build/lib/cinch/roles/jenkins_master/tasks copying cinch/roles/jenkins_master/tasks/pin_plugin.yml -> build/lib/cinch/roles/jenkins_master/tasks copying cinch/roles/jenkins_master/tasks/plugins.yml -> build/lib/cinch/roles/jenkins_master/tasks copying cinch/roles/jenkins_master/tasks/post_configure.yml -> build/lib/cinch/roles/jenkins_master/tasks copying cinch/roles/jenkins_master/tasks/pre_install.yml -> build/lib/cinch/roles/jenkins_master/tasks creating build/lib/cinch/roles/jenkins_master/templates copying cinch/roles/jenkins_master/templates/99-jenkins.conf -> build/lib/cinch/roles/jenkins_master/templates copying cinch/roles/jenkins_master/templates/basic_security.groovy -> build/lib/cinch/roles/jenkins_master/templates copying cinch/roles/jenkins_master/templates/enable-kerberos-sso.groovy -> build/lib/cinch/roles/jenkins_master/templates copying cinch/roles/jenkins_master/templates/init_backup.groovy -> build/lib/cinch/roles/jenkins_master/templates copying cinch/roles/jenkins_master/templates/jenkins_pinned -> build/lib/cinch/roles/jenkins_master/templates copying cinch/roles/jenkins_master/templates/jenkins_root_url.groovy -> build/lib/cinch/roles/jenkins_master/templates copying cinch/roles/jenkins_master/templates/roles_and_ldap_auth.groovy -> build/lib/cinch/roles/jenkins_master/templates copying cinch/roles/jenkins_master/templates/set_slaveport.groovy -> build/lib/cinch/roles/jenkins_master/templates copying cinch/roles/jenkins_master/templates/set_usebrowser.groovy -> build/lib/cinch/roles/jenkins_master/templates copying cinch/roles/jenkins_master/templates/setenvvars.groovy -> build/lib/cinch/roles/jenkins_master/templates copying cinch/roles/jenkins_master/templates/sysconfig_jenkins -> build/lib/cinch/roles/jenkins_master/templates copying cinch/roles/jenkins_master/templates/user.groovy -> build/lib/cinch/roles/jenkins_master/templates creating build/lib/cinch/roles/jenkins_master/templates/etc creating build/lib/cinch/roles/jenkins_master/templates/etc/nginx creating build/lib/cinch/roles/jenkins_master/templates/etc/nginx/conf.d copying cinch/roles/jenkins_master/templates/etc/nginx/conf.d/jenkins_http.conf -> build/lib/cinch/roles/jenkins_master/templates/etc/nginx/conf.d /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.nginx.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.nginx.meta' 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 'cinch.roles.nginx.meta' 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 'cinch.roles.nginx.meta' to be distributed and are already explicitly excluding 'cinch.roles.nginx.meta' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.nginx.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.nginx.tasks' 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 'cinch.roles.nginx.tasks' 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 'cinch.roles.nginx.tasks' to be distributed and are already explicitly excluding 'cinch.roles.nginx.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.nginx.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.nginx.templates' 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 'cinch.roles.nginx.templates' 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 'cinch.roles.nginx.templates' to be distributed and are already explicitly excluding 'cinch.roles.nginx.templates' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.nginx.templates.etc.nginx' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.nginx.templates.etc.nginx' 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 'cinch.roles.nginx.templates.etc.nginx' 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 'cinch.roles.nginx.templates.etc.nginx' to be distributed and are already explicitly excluding 'cinch.roles.nginx.templates.etc.nginx' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.ntp.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.ntp.tasks' 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 'cinch.roles.ntp.tasks' 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 'cinch.roles.ntp.tasks' to be distributed and are already explicitly excluding 'cinch.roles.ntp.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.repositories.defaults' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.repositories.defaults' 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 'cinch.roles.repositories.defaults' 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 'cinch.roles.repositories.defaults' to be distributed and are already explicitly excluding 'cinch.roles.repositories.defaults' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.repositories.handlers' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.repositories.handlers' 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 'cinch.roles.repositories.handlers' 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 'cinch.roles.repositories.handlers' to be distributed and are already explicitly excluding 'cinch.roles.repositories.handlers' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.repositories.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.repositories.tasks' 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 'cinch.roles.repositories.tasks' 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 'cinch.roles.repositories.tasks' to be distributed and are already explicitly excluding 'cinch.roles.repositories.tasks' via `find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`, you can try to use `exclude_package_data`, or `include-package-data=False` in combination with a more fine grained `package-data` configuration. You can read more about "package data files" on setuptools documentation page: - https://setuptools.pypa.io/en/latest/userguide/datafiles.html [^1]: For Python, any directory (with suitable naming) can be imported, even if it does not contain any `.py` files. On the other hand, currently there is no concept of package data directory, all directories are treated like packages. ******************************************************************************** !! check.warn(importable) /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _Warning: Package 'cinch.roles.upload_files.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'cinch.roles.upload_files.tasks' 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 'cinch.roles.upload_files.tasks' 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 'cinch.roles.upload_files.tasks' to be distributed and are already explicitly excluding 'cinch.roles.upload_files.tasks' 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 cinch/roles/jenkins_master/templates/etc/nginx/conf.d/jenkins_https.conf -> build/lib/cinch/roles/jenkins_master/templates/etc/nginx/conf.d creating build/lib/cinch/roles/jenkins_master/vars copying cinch/roles/jenkins_master/vars/main.yml -> build/lib/cinch/roles/jenkins_master/vars creating build/lib/cinch/roles/jenkins_master_stop creating build/lib/cinch/roles/jenkins_master_stop/tasks copying cinch/roles/jenkins_master_stop/tasks/main.yml -> build/lib/cinch/roles/jenkins_master_stop/tasks creating build/lib/cinch/roles/jenkins_slave creating build/lib/cinch/roles/jenkins_slave/defaults copying cinch/roles/jenkins_slave/defaults/main.yml -> build/lib/cinch/roles/jenkins_slave/defaults creating build/lib/cinch/roles/jenkins_slave/handlers copying cinch/roles/jenkins_slave/handlers/main.yml -> build/lib/cinch/roles/jenkins_slave/handlers creating build/lib/cinch/roles/jenkins_slave/tasks copying cinch/roles/jenkins_slave/tasks/check_swarm_errors.yml -> build/lib/cinch/roles/jenkins_slave/tasks copying cinch/roles/jenkins_slave/tasks/check_swarm_systemd.yml -> build/lib/cinch/roles/jenkins_slave/tasks copying cinch/roles/jenkins_slave/tasks/check_swarm_upstart.yml -> build/lib/cinch/roles/jenkins_slave/tasks copying cinch/roles/jenkins_slave/tasks/main.yml -> build/lib/cinch/roles/jenkins_slave/tasks creating build/lib/cinch/roles/jenkins_slave/templates copying cinch/roles/jenkins_slave/templates/swarm.service -> build/lib/cinch/roles/jenkins_slave/templates copying cinch/roles/jenkins_slave/templates/swarm.upstart.conf -> build/lib/cinch/roles/jenkins_slave/templates copying cinch/roles/jenkins_slave/templates/sysconfig_jenkins_swarm -> build/lib/cinch/roles/jenkins_slave/templates creating build/lib/cinch/roles/jenkins_slave_container_wrapup creating build/lib/cinch/roles/jenkins_slave_container_wrapup/defaults copying cinch/roles/jenkins_slave_container_wrapup/defaults/main.yml -> build/lib/cinch/roles/jenkins_slave_container_wrapup/defaults creating build/lib/cinch/roles/jenkins_slave_container_wrapup/tasks copying cinch/roles/jenkins_slave_container_wrapup/tasks/main.yml -> build/lib/cinch/roles/jenkins_slave_container_wrapup/tasks creating build/lib/cinch/roles/jenkins_slave_container_wrapup/templates copying cinch/roles/jenkins_slave_container_wrapup/templates/jmaster.sh -> build/lib/cinch/roles/jenkins_slave_container_wrapup/templates copying cinch/roles/jenkins_slave_container_wrapup/templates/jswarm.sh -> build/lib/cinch/roles/jenkins_slave_container_wrapup/templates creating build/lib/cinch/roles/jenkins_slave_teardown creating build/lib/cinch/roles/jenkins_slave_teardown/tasks copying cinch/roles/jenkins_slave_teardown/tasks/main.yml -> build/lib/cinch/roles/jenkins_slave_teardown/tasks creating build/lib/cinch/roles/nginx creating build/lib/cinch/roles/nginx/defaults copying cinch/roles/nginx/defaults/main.yml -> build/lib/cinch/roles/nginx/defaults creating build/lib/cinch/roles/nginx/files creating build/lib/cinch/roles/nginx/files/etc creating build/lib/cinch/roles/nginx/files/etc/logrotate.d copying cinch/roles/nginx/files/etc/logrotate.d/nginx -> build/lib/cinch/roles/nginx/files/etc/logrotate.d creating build/lib/cinch/roles/nginx/handlers copying cinch/roles/nginx/handlers/main.yml -> build/lib/cinch/roles/nginx/handlers creating build/lib/cinch/roles/nginx/meta copying cinch/roles/nginx/meta/main.yml -> build/lib/cinch/roles/nginx/meta creating build/lib/cinch/roles/nginx/tasks copying cinch/roles/nginx/tasks/kerberos-setup.yml -> build/lib/cinch/roles/nginx/tasks copying cinch/roles/nginx/tasks/main.yml -> build/lib/cinch/roles/nginx/tasks copying cinch/roles/nginx/tasks/nginx.yml -> build/lib/cinch/roles/nginx/tasks copying cinch/roles/nginx/tasks/selinux.yml -> build/lib/cinch/roles/nginx/tasks copying cinch/roles/nginx/tasks/ssl-setup.yml -> build/lib/cinch/roles/nginx/tasks creating build/lib/cinch/roles/nginx/templates copying cinch/roles/nginx/templates/example_ssl.conf -> build/lib/cinch/roles/nginx/templates creating build/lib/cinch/roles/nginx/templates/etc creating build/lib/cinch/roles/nginx/templates/etc/nginx copying cinch/roles/nginx/templates/etc/nginx/nginx.conf -> build/lib/cinch/roles/nginx/templates/etc/nginx creating build/lib/cinch/roles/nginx/templates/etc/nginx/conf.d copying cinch/roles/nginx/templates/etc/nginx/conf.d/errors.conf.snippet -> build/lib/cinch/roles/nginx/templates/etc/nginx/conf.d copying cinch/roles/nginx/templates/etc/nginx/conf.d/monitor.conf.snippet -> build/lib/cinch/roles/nginx/templates/etc/nginx/conf.d creating build/lib/cinch/roles/ntp creating build/lib/cinch/roles/ntp/tasks copying cinch/roles/ntp/tasks/main.yml -> build/lib/cinch/roles/ntp/tasks creating build/lib/cinch/roles/repositories creating build/lib/cinch/roles/repositories/defaults copying cinch/roles/repositories/defaults/main.yml -> build/lib/cinch/roles/repositories/defaults creating build/lib/cinch/roles/repositories/handlers copying cinch/roles/repositories/handlers/main.yml -> build/lib/cinch/roles/repositories/handlers creating build/lib/cinch/roles/repositories/tasks copying cinch/roles/repositories/tasks/main.yml -> build/lib/cinch/roles/repositories/tasks copying cinch/roles/repositories/tasks/repositories.yml -> build/lib/cinch/roles/repositories/tasks copying cinch/roles/repositories/tasks/repository_download.yml -> build/lib/cinch/roles/repositories/tasks creating build/lib/cinch/roles/upload_files creating build/lib/cinch/roles/upload_files/tasks copying cinch/roles/upload_files/tasks/main.yml -> build/lib/cinch/roles/upload_files/tasks + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.AW0pBY + umask 022 + cd /builddir/build/BUILD + '[' /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch '!=' / ']' + rm -rf /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch ++ dirname /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch + mkdir -p /builddir/build/BUILDROOT + mkdir /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch + CFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables -fno-omit-frame-pointer ' + export CFLAGS + CXXFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables -fno-omit-frame-pointer ' + export CXXFLAGS + FFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables -fno-omit-frame-pointer -I/usr/lib/gfortran/modules ' + export FFLAGS + FCFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables -fno-omit-frame-pointer -I/usr/lib/gfortran/modules ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none -Cforce-frame-pointers=yes --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd cinch-1.4.0 + CFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -fasynchronous-unwind-tables -fno-omit-frame-pointer ' + LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld-errors -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -Wl,--build-id=sha1 ' + /usr/bin/python3 setup.py install -O1 --skip-build --root /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch --prefix /usr running install /usr/lib/python3.12/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` directly. Instead, use pypa/build, pypa/installer or other standards-based tools. Follow the current Python packaging guidelines when building Python RPM packages. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html and https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ for details. ******************************************************************************** !! self.initialize_options() running install_lib creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12 creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/tests creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/tests/ansible_lint_rules copying build/lib/tests/ansible_lint_rules/NoFormattingInWhenRule.py -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/tests/ansible_lint_rules copying build/lib/tests/ansible_lint_rules/__init__.py -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/tests/ansible_lint_rules copying build/lib/tests/__init__.py -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/tests copying build/lib/tests/test_cli.py -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/tests creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch copying build/lib/cinch/teardown.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/bin copying build/lib/cinch/bin/wrappers.py -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/bin copying build/lib/cinch/bin/__init__.py -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/bin copying build/lib/cinch/bin/entry_point.py -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/bin creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/files creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/files/jenkins-plugin-lists copying build/lib/cinch/files/jenkins-plugin-lists/default-test.txt -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/files/jenkins-plugin-lists copying build/lib/cinch/files/jenkins-plugin-lists/default.txt -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/files/jenkins-plugin-lists copying build/lib/cinch/files/jenkins-plugin-lists/optional.txt -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/files/jenkins-plugin-lists copying build/lib/cinch/files/jenkins-plugin-lists/README -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/files/jenkins-plugin-lists copying build/lib/cinch/files/jenkins-plugin-lists/optional-test.txt -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/files/jenkins-plugin-lists copying build/lib/cinch/site.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/group_vars copying build/lib/cinch/group_vars/all -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/group_vars copying build/lib/cinch/group_vars/cent7 -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/group_vars copying build/lib/cinch/group_vars/rhel7 -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/group_vars copying build/lib/cinch/group_vars/jenkins_docker_slave -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/group_vars copying build/lib/cinch/group_vars/fedora -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/group_vars copying build/lib/cinch/group_vars/jenkins_slave -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/group_vars copying build/lib/cinch/group_vars/cent6 -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/group_vars copying build/lib/cinch/group_vars/rhel8 -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/group_vars copying build/lib/cinch/group_vars/jenkins_master -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/group_vars copying build/lib/cinch/group_vars/rhel6 -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/group_vars creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/check_ssh creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/check_ssh/defaults copying build/lib/cinch/roles/check_ssh/defaults/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/check_ssh/defaults creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/check_ssh/tasks copying build/lib/cinch/roles/check_ssh/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/check_ssh/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/defaults copying build/lib/cinch/roles/nginx/defaults/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/defaults creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/meta copying build/lib/cinch/roles/nginx/meta/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/meta creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/handlers copying build/lib/cinch/roles/nginx/handlers/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/handlers creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/files creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/files/etc creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/files/etc/logrotate.d copying build/lib/cinch/roles/nginx/files/etc/logrotate.d/nginx -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/files/etc/logrotate.d creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/tasks copying build/lib/cinch/roles/nginx/tasks/ssl-setup.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/tasks copying build/lib/cinch/roles/nginx/tasks/kerberos-setup.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/tasks copying build/lib/cinch/roles/nginx/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/tasks copying build/lib/cinch/roles/nginx/tasks/nginx.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/tasks copying build/lib/cinch/roles/nginx/tasks/selinux.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/templates creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/templates/etc creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/templates/etc/nginx creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/templates/etc/nginx/conf.d copying build/lib/cinch/roles/nginx/templates/etc/nginx/conf.d/monitor.conf.snippet -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/templates/etc/nginx/conf.d copying build/lib/cinch/roles/nginx/templates/etc/nginx/conf.d/errors.conf.snippet -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/templates/etc/nginx/conf.d copying build/lib/cinch/roles/nginx/templates/etc/nginx/nginx.conf -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/templates/etc/nginx copying build/lib/cinch/roles/nginx/templates/example_ssl.conf -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/nginx/templates creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/repositories creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/repositories/defaults copying build/lib/cinch/roles/repositories/defaults/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/repositories/defaults creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/repositories/handlers copying build/lib/cinch/roles/repositories/handlers/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/repositories/handlers creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/repositories/tasks copying build/lib/cinch/roles/repositories/tasks/repositories.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/repositories/tasks copying build/lib/cinch/roles/repositories/tasks/repository_download.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/repositories/tasks copying build/lib/cinch/roles/repositories/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/repositories/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_docker_slave creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_docker_slave/defaults copying build/lib/cinch/roles/jenkins_docker_slave/defaults/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_docker_slave/defaults creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_docker_slave/tasks copying build/lib/cinch/roles/jenkins_docker_slave/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_docker_slave/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave/defaults copying build/lib/cinch/roles/jenkins_slave/defaults/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave/defaults creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave/handlers copying build/lib/cinch/roles/jenkins_slave/handlers/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave/handlers creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave/tasks copying build/lib/cinch/roles/jenkins_slave/tasks/check_swarm_upstart.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave/tasks copying build/lib/cinch/roles/jenkins_slave/tasks/check_swarm_errors.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave/tasks copying build/lib/cinch/roles/jenkins_slave/tasks/check_swarm_systemd.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave/tasks copying build/lib/cinch/roles/jenkins_slave/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave/templates copying build/lib/cinch/roles/jenkins_slave/templates/swarm.upstart.conf -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave/templates copying build/lib/cinch/roles/jenkins_slave/templates/swarm.service -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave/templates copying build/lib/cinch/roles/jenkins_slave/templates/sysconfig_jenkins_swarm -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave/templates creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave_teardown creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave_teardown/tasks copying build/lib/cinch/roles/jenkins_slave_teardown/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave_teardown/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/ntp creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/ntp/tasks copying build/lib/cinch/roles/ntp/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/ntp/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_common creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_common/defaults copying build/lib/cinch/roles/jenkins_common/defaults/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_common/defaults creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_common/handlers copying build/lib/cinch/roles/jenkins_common/handlers/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_common/handlers creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_common/tasks copying build/lib/cinch/roles/jenkins_common/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_common/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_common/vars copying build/lib/cinch/roles/jenkins_common/vars/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_common/vars creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/dockerize creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/dockerize/defaults copying build/lib/cinch/roles/dockerize/defaults/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/dockerize/defaults creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/dockerize/tasks copying build/lib/cinch/roles/dockerize/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/dockerize/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/defaults copying build/lib/cinch/roles/jenkins_master/defaults/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/defaults creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/handlers copying build/lib/cinch/roles/jenkins_master/handlers/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/handlers creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/files copying build/lib/cinch/roles/jenkins_master/files/mass_disable.groovy -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/files copying build/lib/cinch/roles/jenkins_master/files/set_env.groovy -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/files creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/tasks copying build/lib/cinch/roles/jenkins_master/tasks/pin_plugin.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/tasks copying build/lib/cinch/roles/jenkins_master/tasks/pre_install.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/tasks copying build/lib/cinch/roles/jenkins_master/tasks/install.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/tasks copying build/lib/cinch/roles/jenkins_master/tasks/configure.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/tasks copying build/lib/cinch/roles/jenkins_master/tasks/ensure_up.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/tasks copying build/lib/cinch/roles/jenkins_master/tasks/firewalld.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/tasks copying build/lib/cinch/roles/jenkins_master/tasks/post_configure.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/tasks copying build/lib/cinch/roles/jenkins_master/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/tasks copying build/lib/cinch/roles/jenkins_master/tasks/plugins.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/vars copying build/lib/cinch/roles/jenkins_master/vars/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/vars creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates copying build/lib/cinch/roles/jenkins_master/templates/set_usebrowser.groovy -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates/etc creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates/etc/nginx creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates/etc/nginx/conf.d copying build/lib/cinch/roles/jenkins_master/templates/etc/nginx/conf.d/jenkins_https.conf -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates/etc/nginx/conf.d copying build/lib/cinch/roles/jenkins_master/templates/etc/nginx/conf.d/jenkins_http.conf -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates/etc/nginx/conf.d copying build/lib/cinch/roles/jenkins_master/templates/jenkins_root_url.groovy -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates copying build/lib/cinch/roles/jenkins_master/templates/roles_and_ldap_auth.groovy -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates copying build/lib/cinch/roles/jenkins_master/templates/sysconfig_jenkins -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates copying build/lib/cinch/roles/jenkins_master/templates/set_slaveport.groovy -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates copying build/lib/cinch/roles/jenkins_master/templates/99-jenkins.conf -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates copying build/lib/cinch/roles/jenkins_master/templates/user.groovy -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates copying build/lib/cinch/roles/jenkins_master/templates/basic_security.groovy -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates copying build/lib/cinch/roles/jenkins_master/templates/init_backup.groovy -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates copying build/lib/cinch/roles/jenkins_master/templates/setenvvars.groovy -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates copying build/lib/cinch/roles/jenkins_master/templates/jenkins_pinned -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates copying build/lib/cinch/roles/jenkins_master/templates/enable-kerberos-sso.groovy -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master/templates creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/certificate_authority creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/certificate_authority/defaults copying build/lib/cinch/roles/certificate_authority/defaults/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/certificate_authority/defaults creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/certificate_authority/handlers copying build/lib/cinch/roles/certificate_authority/handlers/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/certificate_authority/handlers creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/certificate_authority/tasks copying build/lib/cinch/roles/certificate_authority/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/certificate_authority/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/upload_files creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/upload_files/tasks copying build/lib/cinch/roles/upload_files/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/upload_files/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master_stop creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master_stop/tasks copying build/lib/cinch/roles/jenkins_master_stop/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_master_stop/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/beaker-client creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/beaker-client/defaults copying build/lib/cinch/roles/beaker-client/defaults/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/beaker-client/defaults creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/beaker-client/tasks copying build/lib/cinch/roles/beaker-client/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/beaker-client/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/beaker-client/templates creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/beaker-client/templates/etc creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/beaker-client/templates/etc/beaker copying build/lib/cinch/roles/beaker-client/templates/etc/beaker/client.conf -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/beaker-client/templates/etc/beaker creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave_container_wrapup creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave_container_wrapup/defaults copying build/lib/cinch/roles/jenkins_slave_container_wrapup/defaults/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave_container_wrapup/defaults creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave_container_wrapup/tasks copying build/lib/cinch/roles/jenkins_slave_container_wrapup/tasks/main.yml -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave_container_wrapup/tasks creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave_container_wrapup/templates copying build/lib/cinch/roles/jenkins_slave_container_wrapup/templates/jmaster.sh -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave_container_wrapup/templates copying build/lib/cinch/roles/jenkins_slave_container_wrapup/templates/jswarm.sh -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave_container_wrapup/templates copying build/lib/cinch/__init__.py -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch creating /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/library copying build/lib/cinch/library/line_match.py -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/library copying build/lib/cinch/library/jenkins_user_api.py -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/library copying build/lib/cinch/library/jenkins_script.py -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/library copying build/lib/cinch/library/jenkins_cli_user.py -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/library copying build/lib/cinch/library/jenkins_update_center.py -> /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/library byte-compiling /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/tests/ansible_lint_rules/NoFormattingInWhenRule.py to NoFormattingInWhenRule.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/tests/ansible_lint_rules/__init__.py to __init__.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/tests/__init__.py to __init__.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/tests/test_cli.py to test_cli.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/bin/wrappers.py to wrappers.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/bin/__init__.py to __init__.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/bin/entry_point.py to entry_point.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/__init__.py to __init__.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/library/line_match.py to line_match.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/library/jenkins_user_api.py to jenkins_user_api.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/library/jenkins_script.py to jenkins_script.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/library/jenkins_cli_user.py to jenkins_cli_user.cpython-312.pyc byte-compiling /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch/library/jenkins_update_center.py to jenkins_update_center.cpython-312.pyc writing byte-compilation script '/tmp/tmpnkprlc9z.py' /usr/bin/python3 /tmp/tmpnkprlc9z.py removing /tmp/tmpnkprlc9z.py running install_egg_info running egg_info writing cinch.egg-info/PKG-INFO writing dependency_links to cinch.egg-info/dependency_links.txt writing entry points to cinch.egg-info/entry_points.txt writing requirements to cinch.egg-info/requires.txt writing top-level names to cinch.egg-info/top_level.txt reading manifest file 'cinch.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' adding license file 'LICENSE' writing manifest file 'cinch.egg-info/SOURCES.txt' Copying cinch.egg-info to /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/cinch-1.4.0-py3.12.egg-info running install_scripts Installing cinch script to /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/bin Installing teardown script to /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/bin + rm -rfv /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/bin/__pycache__ + rm -rf /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12/site-packages/tests + /usr/bin/find-debuginfo -j32 --strict-build-id -m -i --build-id-seed 1.4.0-18.fc41 --unique-debug-suffix -1.4.0-18.fc41.noarch --unique-debug-src-base cinch-1.4.0-18.fc41.noarch --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 50000000 -S debugsourcefiles.list /builddir/build/BUILD/cinch-1.4.0 find-debuginfo: starting Extracting debug info from 0 files Creating .debug symlinks for symlinks to ELF files find: ‘debug’: No such file or directory find-debuginfo: done + /usr/lib/rpm/check-buildroot + /usr/lib/rpm/redhat/brp-ldconfig + /usr/lib/rpm/brp-compress + /usr/lib/rpm/redhat/brp-strip-lto /usr/bin/strip + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/redhat/brp-mangle-shebangs mangling shebang in /usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave_container_wrapup/templates/jmaster.sh from /bin/bash -xe to #!/usr/bin/bash -xe mangling shebang in /usr/lib/python3.12/site-packages/cinch/roles/jenkins_slave_container_wrapup/templates/jswarm.sh from /bin/bash -xe to #!/usr/bin/bash -xe + /usr/lib/rpm/brp-remove-la-files + env /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j32 Bytecompiling .py files below /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/lib/python3.12 using python3.12 + /usr/lib/rpm/redhat/brp-python-hardlink Processing files: cinch-1.4.0-18.fc41.noarch Executing(%doc): /bin/sh -e /var/tmp/rpm-tmp.CTLMZe + umask 022 + cd /builddir/build/BUILD + cd cinch-1.4.0 + DOCDIR=/builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/share/doc/cinch + export LC_ALL= + LC_ALL= + export DOCDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/share/doc/cinch + cp -pr /builddir/build/BUILD/cinch-1.4.0/README.md /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/share/doc/cinch + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /var/tmp/rpm-tmp.oc8HRy + umask 022 + cd /builddir/build/BUILD + cd cinch-1.4.0 + LICENSEDIR=/builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/share/licenses/cinch + export LC_ALL= + LC_ALL= + export LICENSEDIR + /usr/bin/mkdir -p /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/share/licenses/cinch + cp -pr /builddir/build/BUILD/cinch-1.4.0/LICENSE /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch/usr/share/licenses/cinch + RPM_EC=0 ++ jobs -p + exit 0 Provides: cinch = 1.4.0-18.fc41 python3.12dist(cinch) = 1.4 python3dist(cinch) = 1.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: /usr/bin/bash /usr/bin/python3 python(abi) = 3.12 python3.12dist(ansible) >= 2.4 python3.12dist(plumbum) >= 1.6 Checking for unpackaged file(s): /usr/lib/rpm/check-files /builddir/build/BUILDROOT/cinch-1.4.0-18.fc41.noarch Wrote: /builddir/build/RPMS/cinch-1.4.0-18.fc41.noarch.rpm Child return code was: 0