D: [iurt_root_command] chroot Building target platforms: noarch Building for target noarch Installing /home/pterjan/rpmbuild/SRPMS/molecule-4.0.1-4.mga10.src.rpm Executing(%mkbuilddir): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.toXnW9 + umask 022 + cd /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + test -d /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + /usr/bin/rm -rf /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + /usr/bin/mkdir -p /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + /usr/bin/mkdir -p /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/SPECPARTS + RPM_EC=0 ++ jobs -p + exit 0 Executing(%prep): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.2IvXcM + umask 022 + cd /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + cd /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + rm -rf molecule-4.0.1 + /usr/lib/rpm/rpmuncompress -x /home/pterjan/rpmbuild/SOURCES/molecule-4.0.1.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd molecule-4.0.1 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + perl -pi -e 's|cerberus .*|cerberus > 1.3.4|' setup.cfg + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.scjxd0 + umask 022 + cd /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd molecule-4.0.1 + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + mkdir -p /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/.pyproject-builddir + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + VALAFLAGS=-g + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + CXX=g++ + TMPDIR=/home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/.pyproject-builddir + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_wheel.py /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/pyproject-wheeldir Processing /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1 Preparing metadata (pyproject.toml): started Running command Preparing metadata (pyproject.toml) /usr/lib/python3.12/site-packages/setuptools_scm/git.py:308: UserWarning: git archive did not support describe output warnings.warn("git archive did not support describe output") running dist_info creating /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/.pyproject-builddir/pip-modern-metadata-fe2admio/molecule.egg-info writing /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/.pyproject-builddir/pip-modern-metadata-fe2admio/molecule.egg-info/PKG-INFO writing dependency_links to /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/.pyproject-builddir/pip-modern-metadata-fe2admio/molecule.egg-info/dependency_links.txt writing entry points to /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/.pyproject-builddir/pip-modern-metadata-fe2admio/molecule.egg-info/entry_points.txt writing requirements to /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/.pyproject-builddir/pip-modern-metadata-fe2admio/molecule.egg-info/requires.txt writing top-level names to /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/.pyproject-builddir/pip-modern-metadata-fe2admio/molecule.egg-info/top_level.txt writing manifest file '/home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/.pyproject-builddir/pip-modern-metadata-fe2admio/molecule.egg-info/SOURCES.txt' WARNING setuptools_scm._file_finders.git git archive detected - fallback to listing all files reading manifest template 'MANIFEST.in' no previously-included directories found matching 'asset' adding license file 'LICENSE' writing manifest file '/home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/.pyproject-builddir/pip-modern-metadata-fe2admio/molecule.egg-info/SOURCES.txt' creating '/home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/.pyproject-builddir/pip-modern-metadata-fe2admio/molecule-4.0.1.dist-info' Preparing metadata (pyproject.toml): finished with status 'done' Building wheels for collected packages: molecule Building wheel for molecule (pyproject.toml): started Running command Building wheel for molecule (pyproject.toml) /usr/lib/python3.12/site-packages/setuptools_scm/git.py:308: UserWarning: git archive did not support describe output warnings.warn("git archive did not support describe output") running bdist_wheel running build running build_py creating build/lib/molecule copying src/molecule/text.py -> build/lib/molecule copying src/molecule/app.py -> build/lib/molecule copying src/molecule/status.py -> build/lib/molecule copying src/molecule/scenarios.py -> build/lib/molecule copying src/molecule/interpolation.py -> build/lib/molecule copying src/molecule/shell.py -> build/lib/molecule copying src/molecule/console.py -> build/lib/molecule copying src/molecule/logger.py -> build/lib/molecule copying src/molecule/__main__.py -> build/lib/molecule copying src/molecule/config.py -> build/lib/molecule copying src/molecule/constants.py -> build/lib/molecule copying src/molecule/__init__.py -> build/lib/molecule copying src/molecule/scenario.py -> build/lib/molecule copying src/molecule/util.py -> build/lib/molecule copying src/molecule/api.py -> build/lib/molecule copying src/molecule/platforms.py -> build/lib/molecule copying src/molecule/state.py -> build/lib/molecule creating build/lib/molecule/model copying src/molecule/model/schema_v3.py -> build/lib/molecule/model copying src/molecule/model/__init__.py -> build/lib/molecule/model creating build/lib/molecule/test copying src/molecule/test/conftest.py -> build/lib/molecule/test copying src/molecule/test/__init__.py -> build/lib/molecule/test creating build/lib/molecule/driver copying src/molecule/driver/delegated.py -> build/lib/molecule/driver copying src/molecule/driver/__init__.py -> build/lib/molecule/driver copying src/molecule/driver/base.py -> build/lib/molecule/driver creating build/lib/molecule/lint copying src/molecule/lint/__init__.py -> build/lib/molecule/lint copying src/molecule/lint/base.py -> build/lib/molecule/lint creating build/lib/molecule/verifier copying src/molecule/verifier/ansible.py -> build/lib/molecule/verifier copying src/molecule/verifier/__init__.py -> build/lib/molecule/verifier copying src/molecule/verifier/testinfra.py -> build/lib/molecule/verifier copying src/molecule/verifier/base.py -> build/lib/molecule/verifier creating build/lib/molecule/provisioner copying src/molecule/provisioner/ansible_playbooks.py -> build/lib/molecule/provisioner copying src/molecule/provisioner/ansible.py -> build/lib/molecule/provisioner copying src/molecule/provisioner/__init__.py -> build/lib/molecule/provisioner copying src/molecule/provisioner/base.py -> build/lib/molecule/provisioner copying src/molecule/provisioner/ansible_playbook.py -> build/lib/molecule/provisioner creating build/lib/molecule/dependency copying src/molecule/dependency/shell.py -> build/lib/molecule/dependency copying src/molecule/dependency/__init__.py -> build/lib/molecule/dependency copying src/molecule/dependency/base.py -> build/lib/molecule/dependency creating build/lib/molecule/command copying src/molecule/command/drivers.py -> build/lib/molecule/command copying src/molecule/command/reset.py -> build/lib/molecule/command copying src/molecule/command/destroy.py -> build/lib/molecule/command copying src/molecule/command/matrix.py -> build/lib/molecule/command copying src/molecule/command/prepare.py -> build/lib/molecule/command copying src/molecule/command/verify.py -> build/lib/molecule/command copying src/molecule/command/list.py -> build/lib/molecule/command copying src/molecule/command/idempotence.py -> build/lib/molecule/command copying src/molecule/command/lint.py -> build/lib/molecule/command copying src/molecule/command/test.py -> build/lib/molecule/command copying src/molecule/command/converge.py -> build/lib/molecule/command copying src/molecule/command/check.py -> build/lib/molecule/command copying src/molecule/command/side_effect.py -> build/lib/molecule/command copying src/molecule/command/__init__.py -> build/lib/molecule/command copying src/molecule/command/cleanup.py -> build/lib/molecule/command copying src/molecule/command/login.py -> build/lib/molecule/command copying src/molecule/command/syntax.py -> build/lib/molecule/command copying src/molecule/command/dependency.py -> build/lib/molecule/command copying src/molecule/command/base.py -> build/lib/molecule/command copying src/molecule/command/create.py -> build/lib/molecule/command creating build/lib/molecule/test/unit copying src/molecule/test/unit/test_text.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/test_util.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/test_interpolation.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/conftest.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/test_config.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/test_scenarios_ordered.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/test_platforms.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/test_status.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/test_scenarios.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/__init__.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/test_shell.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/test_api.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/test_state.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/test_logger.py -> build/lib/molecule/test/unit copying src/molecule/test/unit/test_scenario.py -> build/lib/molecule/test/unit creating build/lib/molecule/test/functional copying src/molecule/test/functional/conftest.py -> build/lib/molecule/test/functional copying src/molecule/test/functional/test_command.py -> build/lib/molecule/test/functional copying src/molecule/test/functional/__init__.py -> build/lib/molecule/test/functional creating build/lib/molecule/test/unit/model copying src/molecule/test/unit/model/__init__.py -> build/lib/molecule/test/unit/model creating build/lib/molecule/test/unit/driver copying src/molecule/test/unit/driver/test_delegated.py -> build/lib/molecule/test/unit/driver copying src/molecule/test/unit/driver/__init__.py -> build/lib/molecule/test/unit/driver creating build/lib/molecule/test/unit/lint copying src/molecule/test/unit/lint/__init__.py -> build/lib/molecule/test/unit/lint creating build/lib/molecule/test/unit/verifier copying src/molecule/test/unit/verifier/test_ansible.py -> build/lib/molecule/test/unit/verifier copying src/molecule/test/unit/verifier/__init__.py -> build/lib/molecule/test/unit/verifier copying src/molecule/test/unit/verifier/test_testinfra.py -> build/lib/molecule/test/unit/verifier creating build/lib/molecule/test/unit/provisioner copying src/molecule/test/unit/provisioner/test_ansible_playbooks.py -> build/lib/molecule/test/unit/provisioner copying src/molecule/test/unit/provisioner/test_ansible.py -> build/lib/molecule/test/unit/provisioner copying src/molecule/test/unit/provisioner/__init__.py -> build/lib/molecule/test/unit/provisioner copying src/molecule/test/unit/provisioner/test_ansible_playbook.py -> build/lib/molecule/test/unit/provisioner creating build/lib/molecule/test/unit/dependency copying src/molecule/test/unit/dependency/__init__.py -> build/lib/molecule/test/unit/dependency copying src/molecule/test/unit/dependency/test_shell.py -> build/lib/molecule/test/unit/dependency creating build/lib/molecule/test/unit/cookiecutter copying src/molecule/test/unit/cookiecutter/test_molecule.py -> build/lib/molecule/test/unit/cookiecutter copying src/molecule/test/unit/cookiecutter/__init__.py -> build/lib/molecule/test/unit/cookiecutter creating build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_test.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_verify.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_matrix.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_syntax.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_prepare.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_cleanup.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/conftest.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_dependency.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_destroy.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_base.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_list.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_converge.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_check.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_create.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_lint.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_login.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/__init__.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_side_effect.py -> build/lib/molecule/test/unit/command copying src/molecule/test/unit/command/test_idempotence.py -> build/lib/molecule/test/unit/command creating build/lib/molecule/test/unit/model/v2 copying src/molecule/test/unit/model/v2/test_platforms_section.py -> build/lib/molecule/test/unit/model/v2 copying src/molecule/test/unit/model/v2/test_schema.py -> build/lib/molecule/test/unit/model/v2 copying src/molecule/test/unit/model/v2/conftest.py -> build/lib/molecule/test/unit/model/v2 copying src/molecule/test/unit/model/v2/test_dependency_section.py -> build/lib/molecule/test/unit/model/v2 copying src/molecule/test/unit/model/v2/test_scenario_section.py -> build/lib/molecule/test/unit/model/v2 copying src/molecule/test/unit/model/v2/test_verifier_section.py -> build/lib/molecule/test/unit/model/v2 copying src/molecule/test/unit/model/v2/test_pre_validate.py -> build/lib/molecule/test/unit/model/v2 copying src/molecule/test/unit/model/v2/__init__.py -> build/lib/molecule/test/unit/model/v2 copying src/molecule/test/unit/model/v2/test_provisioner_section.py -> build/lib/molecule/test/unit/model/v2 copying src/molecule/test/unit/model/v2/test_driver_section.py -> build/lib/molecule/test/unit/model/v2 creating build/lib/molecule/test/unit/dependency/ansible_galaxy copying src/molecule/test/unit/dependency/ansible_galaxy/test_collections.py -> build/lib/molecule/test/unit/dependency/ansible_galaxy copying src/molecule/test/unit/dependency/ansible_galaxy/test_roles.py -> build/lib/molecule/test/unit/dependency/ansible_galaxy copying src/molecule/test/unit/dependency/ansible_galaxy/__init__.py -> build/lib/molecule/test/unit/dependency/ansible_galaxy creating build/lib/molecule/test/unit/command/init copying src/molecule/test/unit/command/init/__init__.py -> build/lib/molecule/test/unit/command/init copying src/molecule/test/unit/command/init/test_role.py -> build/lib/molecule/test/unit/command/init copying src/molecule/test/unit/command/init/test_scenario.py -> build/lib/molecule/test/unit/command/init creating build/lib/molecule/dependency/ansible_galaxy copying src/molecule/dependency/ansible_galaxy/roles.py -> build/lib/molecule/dependency/ansible_galaxy copying src/molecule/dependency/ansible_galaxy/collections.py -> build/lib/molecule/dependency/ansible_galaxy copying src/molecule/dependency/ansible_galaxy/__init__.py -> build/lib/molecule/dependency/ansible_galaxy copying src/molecule/dependency/ansible_galaxy/base.py -> build/lib/molecule/dependency/ansible_galaxy creating build/lib/molecule/command/init copying src/molecule/command/init/__init__.py -> build/lib/molecule/command/init copying src/molecule/command/init/init.py -> build/lib/molecule/command/init copying src/molecule/command/init/scenario.py -> build/lib/molecule/command/init copying src/molecule/command/init/base.py -> build/lib/molecule/command/init copying src/molecule/command/init/role.py -> build/lib/molecule/command/init running egg_info writing src/molecule.egg-info/PKG-INFO writing dependency_links to src/molecule.egg-info/dependency_links.txt writing entry points to src/molecule.egg-info/entry_points.txt writing requirements to src/molecule.egg-info/requires.txt writing top-level names to src/molecule.egg-info/top_level.txt WARNING setuptools_scm._file_finders.git git archive detected - fallback to listing all files reading manifest template 'MANIFEST.in' no previously-included directories found matching 'asset' adding license file 'LICENSE' writing manifest file 'src/molecule.egg-info/SOURCES.txt' /usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'molecule.cookiecutter.molecule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.cookiecutter.molecule' 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 'molecule.cookiecutter.molecule' 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 'molecule.cookiecutter.molecule' to be distributed and are already explicitly excluding 'molecule.cookiecutter.molecule' 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:212: _Warning: Package 'molecule.cookiecutter.scenario.driver.delegated' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.cookiecutter.scenario.driver.delegated' 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 'molecule.cookiecutter.scenario.driver.delegated' 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 'molecule.cookiecutter.scenario.driver.delegated' to be distributed and are already explicitly excluding 'molecule.cookiecutter.scenario.driver.delegated' 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:212: _Warning: Package 'molecule.cookiecutter.scenario.verifier.ansible' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.cookiecutter.scenario.verifier.ansible' 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 'molecule.cookiecutter.scenario.verifier.ansible' 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 'molecule.cookiecutter.scenario.verifier.ansible' to be distributed and are already explicitly excluding 'molecule.cookiecutter.scenario.verifier.ansible' 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:212: _Warning: Package 'molecule.cookiecutter.scenario.verifier.testinfra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.cookiecutter.scenario.verifier.testinfra' 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 'molecule.cookiecutter.scenario.verifier.testinfra' 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 'molecule.cookiecutter.scenario.verifier.testinfra' to be distributed and are already explicitly excluding 'molecule.cookiecutter.scenario.verifier.testinfra' 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:212: _Warning: Package 'molecule.data' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.data' 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 'molecule.data' 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 'molecule.data' to be distributed and are already explicitly excluding 'molecule.data' 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:212: _Warning: Package 'molecule.test.resources' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.resources' 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 'molecule.test.resources' 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 'molecule.test.resources' to be distributed and are already explicitly excluding 'molecule.test.resources' 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:212: _Warning: Package 'molecule.test.resources.invalid_role_template' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.resources.invalid_role_template' 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 'molecule.test.resources.invalid_role_template' 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 'molecule.test.resources.invalid_role_template' to be distributed and are already explicitly excluding 'molecule.test.resources.invalid_role_template' 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:212: _Warning: Package 'molecule.test.resources.invalid_role_template.bad_format' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.resources.invalid_role_template.bad_format' 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 'molecule.test.resources.invalid_role_template.bad_format' 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 'molecule.test.resources.invalid_role_template.bad_format' to be distributed and are already explicitly excluding 'molecule.test.resources.invalid_role_template.bad_format' 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:212: _Warning: Package 'molecule.test.resources.playbooks.delegated' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.resources.playbooks.delegated' 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 'molecule.test.resources.playbooks.delegated' 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 'molecule.test.resources.playbooks.delegated' to be distributed and are already explicitly excluding 'molecule.test.resources.playbooks.delegated' 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:212: _Warning: Package 'molecule.test.resources.playbooks.delegated.inventory.group_vars.all' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.resources.playbooks.delegated.inventory.group_vars.all' 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 'molecule.test.resources.playbooks.delegated.inventory.group_vars.all' 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 'molecule.test.resources.playbooks.delegated.inventory.group_vars.all' to be distributed and are already explicitly excluding 'molecule.test.resources.playbooks.delegated.inventory.group_vars.all' 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:212: _Warning: Package 'molecule.test.resources.roles.molecule.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.resources.roles.molecule.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 'molecule.test.resources.roles.molecule.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 'molecule.test.resources.roles.molecule.meta' to be distributed and are already explicitly excluding 'molecule.test.resources.roles.molecule.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:212: _Warning: Package 'molecule.test.resources.roles.molecule.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.resources.roles.molecule.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 'molecule.test.resources.roles.molecule.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 'molecule.test.resources.roles.molecule.tasks' to be distributed and are already explicitly excluding 'molecule.test.resources.roles.molecule.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:212: _Warning: Package 'molecule.test.resources.templates' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.resources.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 'molecule.test.resources.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 'molecule.test.resources.templates' to be distributed and are already explicitly excluding 'molecule.test.resources.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:212: _Warning: Package 'molecule.test.scenarios' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios' 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 'molecule.test.scenarios' 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 'molecule.test.scenarios' to be distributed and are already explicitly excluding 'molecule.test.scenarios' 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:212: _Warning: Package 'molecule.test.scenarios.cleanup.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.cleanup.molecule.default' 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 'molecule.test.scenarios.cleanup.molecule.default' 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 'molecule.test.scenarios.cleanup.molecule.default' to be distributed and are already explicitly excluding 'molecule.test.scenarios.cleanup.molecule.default' 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:212: _Warning: Package 'molecule.test.scenarios.cleanup.molecule.default.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.cleanup.molecule.default.tests' 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 'molecule.test.scenarios.cleanup.molecule.default.tests' 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 'molecule.test.scenarios.cleanup.molecule.default.tests' to be distributed and are already explicitly excluding 'molecule.test.scenarios.cleanup.molecule.default.tests' 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:212: _Warning: Package 'molecule.test.scenarios.dependency.molecule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.dependency.molecule' 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 'molecule.test.scenarios.dependency.molecule' 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 'molecule.test.scenarios.dependency.molecule' to be distributed and are already explicitly excluding 'molecule.test.scenarios.dependency.molecule' 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:212: _Warning: Package 'molecule.test.scenarios.dependency.molecule.shell' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.dependency.molecule.shell' 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 'molecule.test.scenarios.dependency.molecule.shell' 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 'molecule.test.scenarios.dependency.molecule.shell' to be distributed and are already explicitly excluding 'molecule.test.scenarios.dependency.molecule.shell' 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:212: _Warning: Package 'molecule.test.scenarios.driver.delegated.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.driver.delegated.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 'molecule.test.scenarios.driver.delegated.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 'molecule.test.scenarios.driver.delegated.meta' to be distributed and are already explicitly excluding 'molecule.test.scenarios.driver.delegated.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:212: _Warning: Package 'molecule.test.scenarios.driver.delegated.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.driver.delegated.molecule.default' 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 'molecule.test.scenarios.driver.delegated.molecule.default' 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 'molecule.test.scenarios.driver.delegated.molecule.default' to be distributed and are already explicitly excluding 'molecule.test.scenarios.driver.delegated.molecule.default' 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:212: _Warning: Package 'molecule.test.scenarios.driver.delegated_invalid_role_name_with_role_name_check_equals_to_1.meta' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.driver.delegated_invalid_role_name_with_role_name_check_equals_to_1.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 'molecule.test.scenarios.driver.delegated_invalid_role_name_with_role_name_check_equals_to_1.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 'molecule.test.scenarios.driver.delegated_invalid_role_name_with_role_name_check_equals_to_1.meta' to be distributed and are already explicitly excluding 'molecule.test.scenarios.driver.delegated_invalid_role_name_with_role_name_check_equals_to_1.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:212: _Warning: Package 'molecule.test.scenarios.driver.delegated_invalid_role_name_with_role_name_check_equals_to_1.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.driver.delegated_invalid_role_name_with_role_name_check_equals_to_1.molecule.default' 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 'molecule.test.scenarios.driver.delegated_invalid_role_name_with_role_name_check_equals_to_1.molecule.default' 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 'molecule.test.scenarios.driver.delegated_invalid_role_name_with_role_name_check_equals_to_1.molecule.default' to be distributed and are already explicitly excluding 'molecule.test.scenarios.driver.delegated_invalid_role_name_with_role_name_check_equals_to_1.molecule.default' 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:212: _Warning: Package 'molecule.test.scenarios.host_group_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.host_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 'molecule.test.scenarios.host_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 'molecule.test.scenarios.host_group_vars' to be distributed and are already explicitly excluding 'molecule.test.scenarios.host_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:212: _Warning: Package 'molecule.test.scenarios.host_group_vars.group_vars.example' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.host_group_vars.group_vars.example' 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 'molecule.test.scenarios.host_group_vars.group_vars.example' 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 'molecule.test.scenarios.host_group_vars.group_vars.example' to be distributed and are already explicitly excluding 'molecule.test.scenarios.host_group_vars.group_vars.example' 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:212: _Warning: Package 'molecule.test.scenarios.host_group_vars.host_vars' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.host_group_vars.host_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 'molecule.test.scenarios.host_group_vars.host_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 'molecule.test.scenarios.host_group_vars.host_vars' to be distributed and are already explicitly excluding 'molecule.test.scenarios.host_group_vars.host_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:212: _Warning: Package 'molecule.test.scenarios.host_group_vars.host_vars.instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.host_group_vars.host_vars.instance' 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 'molecule.test.scenarios.host_group_vars.host_vars.instance' 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 'molecule.test.scenarios.host_group_vars.host_vars.instance' to be distributed and are already explicitly excluding 'molecule.test.scenarios.host_group_vars.host_vars.instance' 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:212: _Warning: Package 'molecule.test.scenarios.host_group_vars.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.host_group_vars.molecule.default' 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 'molecule.test.scenarios.host_group_vars.molecule.default' 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 'molecule.test.scenarios.host_group_vars.molecule.default' to be distributed and are already explicitly excluding 'molecule.test.scenarios.host_group_vars.molecule.default' 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:212: _Warning: Package 'molecule.test.scenarios.host_group_vars.molecule.default.group_vars.example' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.host_group_vars.molecule.default.group_vars.example' 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 'molecule.test.scenarios.host_group_vars.molecule.default.group_vars.example' 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 'molecule.test.scenarios.host_group_vars.molecule.default.group_vars.example' to be distributed and are already explicitly excluding 'molecule.test.scenarios.host_group_vars.molecule.default.group_vars.example' 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:212: _Warning: Package 'molecule.test.scenarios.host_group_vars.molecule.default.host_vars.instance' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.host_group_vars.molecule.default.host_vars.instance' 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 'molecule.test.scenarios.host_group_vars.molecule.default.host_vars.instance' 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 'molecule.test.scenarios.host_group_vars.molecule.default.host_vars.instance' to be distributed and are already explicitly excluding 'molecule.test.scenarios.host_group_vars.molecule.default.host_vars.instance' 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:212: _Warning: Package 'molecule.test.scenarios.host_group_vars.molecule.links' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.host_group_vars.molecule.links' 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 'molecule.test.scenarios.host_group_vars.molecule.links' 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 'molecule.test.scenarios.host_group_vars.molecule.links' to be distributed and are already explicitly excluding 'molecule.test.scenarios.host_group_vars.molecule.links' 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:212: _Warning: Package 'molecule.test.scenarios.idempotence.molecule.raises' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.idempotence.molecule.raises' 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 'molecule.test.scenarios.idempotence.molecule.raises' 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 'molecule.test.scenarios.idempotence.molecule.raises' to be distributed and are already explicitly excluding 'molecule.test.scenarios.idempotence.molecule.raises' 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:212: _Warning: Package 'molecule.test.scenarios.idempotence.tasks' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.idempotence.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 'molecule.test.scenarios.idempotence.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 'molecule.test.scenarios.idempotence.tasks' to be distributed and are already explicitly excluding 'molecule.test.scenarios.idempotence.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:212: _Warning: Package 'molecule.test.scenarios.interpolation.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.interpolation.molecule.default' 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 'molecule.test.scenarios.interpolation.molecule.default' 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 'molecule.test.scenarios.interpolation.molecule.default' to be distributed and are already explicitly excluding 'molecule.test.scenarios.interpolation.molecule.default' 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:212: _Warning: Package 'molecule.test.scenarios.overrride_driver.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.overrride_driver.molecule.default' 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 'molecule.test.scenarios.overrride_driver.molecule.default' 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 'molecule.test.scenarios.overrride_driver.molecule.default' to be distributed and are already explicitly excluding 'molecule.test.scenarios.overrride_driver.molecule.default' 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:212: _Warning: Package 'molecule.test.scenarios.side_effect.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.side_effect.molecule.default' 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 'molecule.test.scenarios.side_effect.molecule.default' 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 'molecule.test.scenarios.side_effect.molecule.default' to be distributed and are already explicitly excluding 'molecule.test.scenarios.side_effect.molecule.default' 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:212: _Warning: Package 'molecule.test.scenarios.side_effect.molecule.default.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.side_effect.molecule.default.tests' 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 'molecule.test.scenarios.side_effect.molecule.default.tests' 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 'molecule.test.scenarios.side_effect.molecule.default.tests' to be distributed and are already explicitly excluding 'molecule.test.scenarios.side_effect.molecule.default.tests' 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:212: _Warning: Package 'molecule.test.scenarios.test_destroy_strategy.molecule.default' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.test_destroy_strategy.molecule.default' 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 'molecule.test.scenarios.test_destroy_strategy.molecule.default' 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 'molecule.test.scenarios.test_destroy_strategy.molecule.default' to be distributed and are already explicitly excluding 'molecule.test.scenarios.test_destroy_strategy.molecule.default' 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:212: _Warning: Package 'molecule.test.scenarios.test_destroy_strategy.molecule.default.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.test_destroy_strategy.molecule.default.tests' 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 'molecule.test.scenarios.test_destroy_strategy.molecule.default.tests' 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 'molecule.test.scenarios.test_destroy_strategy.molecule.default.tests' to be distributed and are already explicitly excluding 'molecule.test.scenarios.test_destroy_strategy.molecule.default.tests' 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:212: _Warning: Package 'molecule.test.scenarios.verifier' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.verifier' 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 'molecule.test.scenarios.verifier' 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 'molecule.test.scenarios.verifier' to be distributed and are already explicitly excluding 'molecule.test.scenarios.verifier' 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:212: _Warning: Package 'molecule.test.scenarios.verifier.molecule.testinfra' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.verifier.molecule.testinfra' 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 'molecule.test.scenarios.verifier.molecule.testinfra' 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 'molecule.test.scenarios.verifier.molecule.testinfra' to be distributed and are already explicitly excluding 'molecule.test.scenarios.verifier.molecule.testinfra' 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:212: _Warning: Package 'molecule.test.scenarios.verifier.molecule' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.verifier.molecule' 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 'molecule.test.scenarios.verifier.molecule' 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 'molecule.test.scenarios.verifier.molecule' to be distributed and are already explicitly excluding 'molecule.test.scenarios.verifier.molecule' 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:212: _Warning: Package 'molecule.test.scenarios.verifier.molecule.testinfra.shared' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.verifier.molecule.testinfra.shared' 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 'molecule.test.scenarios.verifier.molecule.testinfra.shared' 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 'molecule.test.scenarios.verifier.molecule.testinfra.shared' to be distributed and are already explicitly excluding 'molecule.test.scenarios.verifier.molecule.testinfra.shared' 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:212: _Warning: Package 'molecule.test.scenarios.verifier.molecule.testinfra.tests' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'molecule.test.scenarios.verifier.molecule.testinfra.tests' 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 'molecule.test.scenarios.verifier.molecule.testinfra.tests' 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 'molecule.test.scenarios.verifier.molecule.testinfra.tests' to be distributed and are already explicitly excluding 'molecule.test.scenarios.verifier.molecule.testinfra.tests' 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 src/molecule/py.typed -> build/lib/molecule creating build/lib/molecule/cookiecutter/molecule copying src/molecule/cookiecutter/molecule/cookiecutter.json -> build/lib/molecule/cookiecutter/molecule creating build/lib/molecule/cookiecutter/molecule/{{cookiecutter.role_name}} copying src/molecule/cookiecutter/molecule/{{cookiecutter.role_name}}/.yamllint -> build/lib/molecule/cookiecutter/molecule/{{cookiecutter.role_name}} creating build/lib/molecule/cookiecutter/molecule/{{cookiecutter.role_name}}/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} copying src/molecule/cookiecutter/molecule/{{cookiecutter.role_name}}/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/molecule.yml -> build/lib/molecule/cookiecutter/molecule/{{cookiecutter.role_name}}/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} creating build/lib/molecule/cookiecutter/scenario/driver/delegated copying src/molecule/cookiecutter/scenario/driver/delegated/cookiecutter.json -> build/lib/molecule/cookiecutter/scenario/driver/delegated creating build/lib/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} copying src/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/INSTALL.rst -> build/lib/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} copying src/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/converge.yml -> build/lib/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} copying src/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/create.yml -> build/lib/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} copying src/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/destroy.yml -> build/lib/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} creating build/lib/molecule/cookiecutter/scenario/verifier/ansible copying src/molecule/cookiecutter/scenario/verifier/ansible/cookiecutter.json -> build/lib/molecule/cookiecutter/scenario/verifier/ansible creating build/lib/molecule/cookiecutter/scenario/verifier/ansible/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} copying src/molecule/cookiecutter/scenario/verifier/ansible/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/verify.yml -> build/lib/molecule/cookiecutter/scenario/verifier/ansible/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} creating build/lib/molecule/cookiecutter/scenario/verifier/testinfra copying src/molecule/cookiecutter/scenario/verifier/testinfra/cookiecutter.json -> build/lib/molecule/cookiecutter/scenario/verifier/testinfra creating build/lib/molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/{{cookiecutter.verifier_directory}} copying src/molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/{{cookiecutter.verifier_directory}}/conftest.py -> build/lib/molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/{{cookiecutter.verifier_directory}} copying src/molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/{{cookiecutter.verifier_directory}}/test_default.py -> build/lib/molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/{{cookiecutter.verifier_directory}} creating build/lib/molecule/data copying src/molecule/data/Dockerfile.j2 -> build/lib/molecule/data copying src/molecule/data/validate-dockerfile.yml -> build/lib/molecule/data creating build/lib/molecule/test/resources copying src/molecule/test/resources/.yamllint -> build/lib/molecule/test/resources copying src/molecule/test/resources/molecule.yml -> build/lib/molecule/test/resources creating build/lib/molecule/test/resources/invalid_role_template copying src/molecule/test/resources/invalid_role_template/cookiecutter.json -> build/lib/molecule/test/resources/invalid_role_template creating build/lib/molecule/test/resources/invalid_role_template/bad_format copying src/molecule/test/resources/invalid_role_template/bad_format/README.md -> build/lib/molecule/test/resources/invalid_role_template/bad_format creating build/lib/molecule/test/resources/playbooks/delegated copying src/molecule/test/resources/playbooks/delegated/create.yml -> build/lib/molecule/test/resources/playbooks/delegated copying src/molecule/test/resources/playbooks/delegated/destroy.yml -> build/lib/molecule/test/resources/playbooks/delegated creating build/lib/molecule/test/resources/playbooks/delegated/inventory/group_vars/all copying src/molecule/test/resources/playbooks/delegated/inventory/group_vars/all/all.yml -> build/lib/molecule/test/resources/playbooks/delegated/inventory/group_vars/all creating build/lib/molecule/test/resources/roles/molecule/meta copying src/molecule/test/resources/roles/molecule/meta/main.yml -> build/lib/molecule/test/resources/roles/molecule/meta creating build/lib/molecule/test/resources/roles/molecule/tasks copying src/molecule/test/resources/roles/molecule/tasks/main.yml -> build/lib/molecule/test/resources/roles/molecule/tasks creating build/lib/molecule/test/resources/sample-collection copying src/molecule/test/resources/sample-collection/galaxy.yml -> build/lib/molecule/test/resources/sample-collection creating build/lib/molecule/test/resources/sample-collection/molecule/default copying src/molecule/test/resources/sample-collection/molecule/default/converge.yml -> build/lib/molecule/test/resources/sample-collection/molecule/default copying src/molecule/test/resources/sample-collection/molecule/default/molecule.yml -> build/lib/molecule/test/resources/sample-collection/molecule/default creating build/lib/molecule/test/resources/sample-collection/roles/get_rich/tasks copying src/molecule/test/resources/sample-collection/roles/get_rich/tasks/main.yml -> build/lib/molecule/test/resources/sample-collection/roles/get_rich/tasks creating build/lib/molecule/test/resources/templates copying src/molecule/test/resources/templates/cookiecutter.json -> build/lib/molecule/test/resources/templates creating build/lib/molecule/test/resources/templates/{{cookiecutter.repo_name}} copying src/molecule/test/resources/templates/{{cookiecutter.repo_name}}/template.yml -> build/lib/molecule/test/resources/templates/{{cookiecutter.repo_name}} creating build/lib/molecule/test/scenarios copying src/molecule/test/scenarios/.flake8 -> build/lib/molecule/test/scenarios creating build/lib/molecule/test/scenarios/cleanup/molecule/default copying src/molecule/test/scenarios/cleanup/molecule/default/cleanup.yml -> build/lib/molecule/test/scenarios/cleanup/molecule/default copying src/molecule/test/scenarios/cleanup/molecule/default/converge.yml -> build/lib/molecule/test/scenarios/cleanup/molecule/default copying src/molecule/test/scenarios/cleanup/molecule/default/molecule.yml -> build/lib/molecule/test/scenarios/cleanup/molecule/default creating build/lib/molecule/test/scenarios/cleanup/molecule/default/tests copying src/molecule/test/scenarios/cleanup/molecule/default/tests/test_cleanup.py -> build/lib/molecule/test/scenarios/cleanup/molecule/default/tests creating build/lib/molecule/test/scenarios/dependency/molecule/ansible-galaxy copying src/molecule/test/scenarios/dependency/molecule/ansible-galaxy/converge.yml -> build/lib/molecule/test/scenarios/dependency/molecule/ansible-galaxy copying src/molecule/test/scenarios/dependency/molecule/ansible-galaxy/molecule.yml -> build/lib/molecule/test/scenarios/dependency/molecule/ansible-galaxy copying src/molecule/test/scenarios/dependency/molecule/ansible-galaxy/requirements.yml -> build/lib/molecule/test/scenarios/dependency/molecule/ansible-galaxy creating build/lib/molecule/test/scenarios/dependency/molecule/shell copying src/molecule/test/scenarios/dependency/molecule/shell/converge.yml -> build/lib/molecule/test/scenarios/dependency/molecule/shell copying src/molecule/test/scenarios/dependency/molecule/shell/molecule.yml -> build/lib/molecule/test/scenarios/dependency/molecule/shell creating build/lib/molecule/test/scenarios/driver/delegated/meta copying src/molecule/test/scenarios/driver/delegated/meta/main.yml -> build/lib/molecule/test/scenarios/driver/delegated/meta creating build/lib/molecule/test/scenarios/driver/delegated/molecule/default copying src/molecule/test/scenarios/driver/delegated/molecule/default/converge.yml -> build/lib/molecule/test/scenarios/driver/delegated/molecule/default copying src/molecule/test/scenarios/driver/delegated/molecule/default/create.yml -> build/lib/molecule/test/scenarios/driver/delegated/molecule/default copying src/molecule/test/scenarios/driver/delegated/molecule/default/destroy.yml -> build/lib/molecule/test/scenarios/driver/delegated/molecule/default copying src/molecule/test/scenarios/driver/delegated/molecule/default/molecule.yml -> build/lib/molecule/test/scenarios/driver/delegated/molecule/default creating build/lib/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/meta copying src/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/meta/main.yml -> build/lib/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/meta creating build/lib/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default copying src/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default/converge.yml -> build/lib/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default copying src/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default/create.yml -> build/lib/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default copying src/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default/destroy.yml -> build/lib/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default copying src/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default/molecule.yml -> build/lib/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default creating build/lib/molecule/test/scenarios/host_group_vars copying src/molecule/test/scenarios/host_group_vars/hosts -> build/lib/molecule/test/scenarios/host_group_vars creating build/lib/molecule/test/scenarios/host_group_vars/group_vars/example copying src/molecule/test/scenarios/host_group_vars/group_vars/example/all.yml -> build/lib/molecule/test/scenarios/host_group_vars/group_vars/example creating build/lib/molecule/test/scenarios/host_group_vars/host_vars copying src/molecule/test/scenarios/host_group_vars/host_vars/extra-host -> build/lib/molecule/test/scenarios/host_group_vars/host_vars creating build/lib/molecule/test/scenarios/host_group_vars/host_vars/instance copying src/molecule/test/scenarios/host_group_vars/host_vars/instance/all.yml -> build/lib/molecule/test/scenarios/host_group_vars/host_vars/instance creating build/lib/molecule/test/scenarios/host_group_vars/molecule/default copying src/molecule/test/scenarios/host_group_vars/molecule/default/converge.yml -> build/lib/molecule/test/scenarios/host_group_vars/molecule/default copying src/molecule/test/scenarios/host_group_vars/molecule/default/molecule.yml -> build/lib/molecule/test/scenarios/host_group_vars/molecule/default creating build/lib/molecule/test/scenarios/host_group_vars/molecule/default/group_vars/example copying src/molecule/test/scenarios/host_group_vars/molecule/default/group_vars/example/all.yml -> build/lib/molecule/test/scenarios/host_group_vars/molecule/default/group_vars/example creating build/lib/molecule/test/scenarios/host_group_vars/molecule/default/host_vars/instance copying src/molecule/test/scenarios/host_group_vars/molecule/default/host_vars/instance/all.yml -> build/lib/molecule/test/scenarios/host_group_vars/molecule/default/host_vars/instance creating build/lib/molecule/test/scenarios/host_group_vars/molecule/links copying src/molecule/test/scenarios/host_group_vars/molecule/links/converge.yml -> build/lib/molecule/test/scenarios/host_group_vars/molecule/links copying src/molecule/test/scenarios/host_group_vars/molecule/links/molecule.yml -> build/lib/molecule/test/scenarios/host_group_vars/molecule/links creating build/lib/molecule/test/scenarios/idempotence/molecule/raises copying src/molecule/test/scenarios/idempotence/molecule/raises/converge.yml -> build/lib/molecule/test/scenarios/idempotence/molecule/raises copying src/molecule/test/scenarios/idempotence/molecule/raises/molecule.yml -> build/lib/molecule/test/scenarios/idempotence/molecule/raises creating build/lib/molecule/test/scenarios/idempotence/tasks copying src/molecule/test/scenarios/idempotence/tasks/main.yml -> build/lib/molecule/test/scenarios/idempotence/tasks creating build/lib/molecule/test/scenarios/interpolation/molecule/default copying src/molecule/test/scenarios/interpolation/molecule/default/converge.yml -> build/lib/molecule/test/scenarios/interpolation/molecule/default copying src/molecule/test/scenarios/interpolation/molecule/default/molecule.yml -> build/lib/molecule/test/scenarios/interpolation/molecule/default creating build/lib/molecule/test/scenarios/overrride_driver/molecule/default copying src/molecule/test/scenarios/overrride_driver/molecule/default/converge.yml -> build/lib/molecule/test/scenarios/overrride_driver/molecule/default copying src/molecule/test/scenarios/overrride_driver/molecule/default/molecule.yml -> build/lib/molecule/test/scenarios/overrride_driver/molecule/default creating build/lib/molecule/test/scenarios/side_effect/molecule/default copying src/molecule/test/scenarios/side_effect/molecule/default/converge.yml -> build/lib/molecule/test/scenarios/side_effect/molecule/default copying src/molecule/test/scenarios/side_effect/molecule/default/molecule.yml -> build/lib/molecule/test/scenarios/side_effect/molecule/default copying src/molecule/test/scenarios/side_effect/molecule/default/side_effect.yml -> build/lib/molecule/test/scenarios/side_effect/molecule/default creating build/lib/molecule/test/scenarios/side_effect/molecule/default/tests copying src/molecule/test/scenarios/side_effect/molecule/default/tests/test_side_effect.py -> build/lib/molecule/test/scenarios/side_effect/molecule/default/tests creating build/lib/molecule/test/scenarios/test_destroy_strategy/molecule/default copying src/molecule/test/scenarios/test_destroy_strategy/molecule/default/converge.yml -> build/lib/molecule/test/scenarios/test_destroy_strategy/molecule/default copying src/molecule/test/scenarios/test_destroy_strategy/molecule/default/molecule.yml -> build/lib/molecule/test/scenarios/test_destroy_strategy/molecule/default creating build/lib/molecule/test/scenarios/test_destroy_strategy/molecule/default/tests copying src/molecule/test/scenarios/test_destroy_strategy/molecule/default/tests/test_destroy_strategy.py -> build/lib/molecule/test/scenarios/test_destroy_strategy/molecule/default/tests creating build/lib/molecule/test/scenarios/verifier copying src/molecule/test/scenarios/verifier/.pre-commit-config.yaml -> build/lib/molecule/test/scenarios/verifier creating build/lib/molecule/test/scenarios/verifier/molecule/testinfra copying src/molecule/test/scenarios/verifier/molecule/testinfra/converge.yml -> build/lib/molecule/test/scenarios/verifier/molecule/testinfra copying src/molecule/test/scenarios/verifier/molecule/testinfra/molecule.yml -> build/lib/molecule/test/scenarios/verifier/molecule/testinfra creating build/lib/molecule/test/scenarios/verifier/molecule/testinfra-pre-commit copying src/molecule/test/scenarios/verifier/molecule/testinfra-pre-commit/converge.yml -> build/lib/molecule/test/scenarios/verifier/molecule/testinfra-pre-commit copying src/molecule/test/scenarios/verifier/molecule/testinfra-pre-commit/molecule.yml -> build/lib/molecule/test/scenarios/verifier/molecule/testinfra-pre-commit creating build/lib/molecule/test/scenarios/verifier/molecule/testinfra-pre-commit/tests copying src/molecule/test/scenarios/verifier/molecule/testinfra-pre-commit/tests/test_testinfra_pre_commit.py -> build/lib/molecule/test/scenarios/verifier/molecule/testinfra-pre-commit/tests creating build/lib/molecule/test/scenarios/verifier/molecule/testinfra/shared copying src/molecule/test/scenarios/verifier/molecule/testinfra/shared/test_shared.py -> build/lib/molecule/test/scenarios/verifier/molecule/testinfra/shared creating build/lib/molecule/test/scenarios/verifier/molecule/testinfra/tests copying src/molecule/test/scenarios/verifier/molecule/testinfra/tests/test_testinfra.py -> build/lib/molecule/test/scenarios/verifier/molecule/testinfra/tests copying src/molecule/test/functional/.ansible-lint -> build/lib/molecule/test/functional installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/molecule creating build/bdist.linux-x86_64/wheel/molecule/model copying build/lib/molecule/model/schema_v3.py -> build/bdist.linux-x86_64/wheel/./molecule/model copying build/lib/molecule/model/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/model copying build/lib/molecule/text.py -> build/bdist.linux-x86_64/wheel/./molecule copying build/lib/molecule/app.py -> build/bdist.linux-x86_64/wheel/./molecule creating build/bdist.linux-x86_64/wheel/molecule/test creating build/bdist.linux-x86_64/wheel/molecule/test/unit creating build/bdist.linux-x86_64/wheel/molecule/test/unit/model creating build/bdist.linux-x86_64/wheel/molecule/test/unit/model/v2 copying build/lib/molecule/test/unit/model/v2/test_platforms_section.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/model/v2 copying build/lib/molecule/test/unit/model/v2/test_schema.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/model/v2 copying build/lib/molecule/test/unit/model/v2/conftest.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/model/v2 copying build/lib/molecule/test/unit/model/v2/test_dependency_section.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/model/v2 copying build/lib/molecule/test/unit/model/v2/test_scenario_section.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/model/v2 copying build/lib/molecule/test/unit/model/v2/test_verifier_section.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/model/v2 copying build/lib/molecule/test/unit/model/v2/test_pre_validate.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/model/v2 copying build/lib/molecule/test/unit/model/v2/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/model/v2 copying build/lib/molecule/test/unit/model/v2/test_provisioner_section.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/model/v2 copying build/lib/molecule/test/unit/model/v2/test_driver_section.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/model/v2 copying build/lib/molecule/test/unit/model/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/model copying build/lib/molecule/test/unit/test_text.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit copying build/lib/molecule/test/unit/test_util.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit copying build/lib/molecule/test/unit/test_interpolation.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit creating build/bdist.linux-x86_64/wheel/molecule/test/unit/driver copying build/lib/molecule/test/unit/driver/test_delegated.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/driver copying build/lib/molecule/test/unit/driver/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/driver copying build/lib/molecule/test/unit/conftest.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit creating build/bdist.linux-x86_64/wheel/molecule/test/unit/lint copying build/lib/molecule/test/unit/lint/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/lint creating build/bdist.linux-x86_64/wheel/molecule/test/unit/verifier copying build/lib/molecule/test/unit/verifier/test_ansible.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/verifier copying build/lib/molecule/test/unit/verifier/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/verifier copying build/lib/molecule/test/unit/verifier/test_testinfra.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/verifier copying build/lib/molecule/test/unit/test_config.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit creating build/bdist.linux-x86_64/wheel/molecule/test/unit/provisioner copying build/lib/molecule/test/unit/provisioner/test_ansible_playbooks.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/provisioner copying build/lib/molecule/test/unit/provisioner/test_ansible.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/provisioner copying build/lib/molecule/test/unit/provisioner/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/provisioner copying build/lib/molecule/test/unit/provisioner/test_ansible_playbook.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/provisioner copying build/lib/molecule/test/unit/test_scenarios_ordered.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit copying build/lib/molecule/test/unit/test_platforms.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit copying build/lib/molecule/test/unit/test_status.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit creating build/bdist.linux-x86_64/wheel/molecule/test/unit/dependency creating build/bdist.linux-x86_64/wheel/molecule/test/unit/dependency/ansible_galaxy copying build/lib/molecule/test/unit/dependency/ansible_galaxy/test_collections.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/dependency/ansible_galaxy copying build/lib/molecule/test/unit/dependency/ansible_galaxy/test_roles.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/dependency/ansible_galaxy copying build/lib/molecule/test/unit/dependency/ansible_galaxy/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/dependency/ansible_galaxy copying build/lib/molecule/test/unit/dependency/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/dependency copying build/lib/molecule/test/unit/dependency/test_shell.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/dependency copying build/lib/molecule/test/unit/test_scenarios.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit copying build/lib/molecule/test/unit/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit copying build/lib/molecule/test/unit/test_shell.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit copying build/lib/molecule/test/unit/test_api.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit creating build/bdist.linux-x86_64/wheel/molecule/test/unit/cookiecutter copying build/lib/molecule/test/unit/cookiecutter/test_molecule.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/cookiecutter copying build/lib/molecule/test/unit/cookiecutter/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/cookiecutter creating build/bdist.linux-x86_64/wheel/molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_test.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_verify.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_matrix.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_syntax.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_prepare.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_cleanup.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/conftest.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command creating build/bdist.linux-x86_64/wheel/molecule/test/unit/command/init copying build/lib/molecule/test/unit/command/init/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command/init copying build/lib/molecule/test/unit/command/init/test_role.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command/init copying build/lib/molecule/test/unit/command/init/test_scenario.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command/init copying build/lib/molecule/test/unit/command/test_dependency.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_destroy.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_base.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_list.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_converge.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_check.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_create.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_lint.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_login.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_side_effect.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/command/test_idempotence.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit/command copying build/lib/molecule/test/unit/test_state.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit copying build/lib/molecule/test/unit/test_logger.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit copying build/lib/molecule/test/unit/test_scenario.py -> build/bdist.linux-x86_64/wheel/./molecule/test/unit copying build/lib/molecule/test/conftest.py -> build/bdist.linux-x86_64/wheel/./molecule/test creating build/bdist.linux-x86_64/wheel/molecule/test/resources copying build/lib/molecule/test/resources/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/resources creating build/bdist.linux-x86_64/wheel/molecule/test/resources/invalid_role_template copying build/lib/molecule/test/resources/invalid_role_template/cookiecutter.json -> build/bdist.linux-x86_64/wheel/./molecule/test/resources/invalid_role_template creating build/bdist.linux-x86_64/wheel/molecule/test/resources/invalid_role_template/bad_format copying build/lib/molecule/test/resources/invalid_role_template/bad_format/README.md -> build/bdist.linux-x86_64/wheel/./molecule/test/resources/invalid_role_template/bad_format creating build/bdist.linux-x86_64/wheel/molecule/test/resources/templates creating build/bdist.linux-x86_64/wheel/molecule/test/resources/templates/{{cookiecutter.repo_name}} copying build/lib/molecule/test/resources/templates/{{cookiecutter.repo_name}}/template.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/resources/templates/{{cookiecutter.repo_name}} copying build/lib/molecule/test/resources/templates/cookiecutter.json -> build/bdist.linux-x86_64/wheel/./molecule/test/resources/templates creating build/bdist.linux-x86_64/wheel/molecule/test/resources/roles creating build/bdist.linux-x86_64/wheel/molecule/test/resources/roles/molecule creating build/bdist.linux-x86_64/wheel/molecule/test/resources/roles/molecule/tasks copying build/lib/molecule/test/resources/roles/molecule/tasks/main.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/resources/roles/molecule/tasks creating build/bdist.linux-x86_64/wheel/molecule/test/resources/roles/molecule/meta copying build/lib/molecule/test/resources/roles/molecule/meta/main.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/resources/roles/molecule/meta creating build/bdist.linux-x86_64/wheel/molecule/test/resources/playbooks creating build/bdist.linux-x86_64/wheel/molecule/test/resources/playbooks/delegated copying build/lib/molecule/test/resources/playbooks/delegated/destroy.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/resources/playbooks/delegated copying build/lib/molecule/test/resources/playbooks/delegated/create.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/resources/playbooks/delegated creating build/bdist.linux-x86_64/wheel/molecule/test/resources/playbooks/delegated/inventory creating build/bdist.linux-x86_64/wheel/molecule/test/resources/playbooks/delegated/inventory/group_vars creating build/bdist.linux-x86_64/wheel/molecule/test/resources/playbooks/delegated/inventory/group_vars/all copying build/lib/molecule/test/resources/playbooks/delegated/inventory/group_vars/all/all.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/resources/playbooks/delegated/inventory/group_vars/all creating build/bdist.linux-x86_64/wheel/molecule/test/resources/sample-collection copying build/lib/molecule/test/resources/sample-collection/galaxy.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/resources/sample-collection creating build/bdist.linux-x86_64/wheel/molecule/test/resources/sample-collection/roles creating build/bdist.linux-x86_64/wheel/molecule/test/resources/sample-collection/roles/get_rich creating build/bdist.linux-x86_64/wheel/molecule/test/resources/sample-collection/roles/get_rich/tasks copying build/lib/molecule/test/resources/sample-collection/roles/get_rich/tasks/main.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/resources/sample-collection/roles/get_rich/tasks creating build/bdist.linux-x86_64/wheel/molecule/test/resources/sample-collection/molecule creating build/bdist.linux-x86_64/wheel/molecule/test/resources/sample-collection/molecule/default copying build/lib/molecule/test/resources/sample-collection/molecule/default/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/resources/sample-collection/molecule/default copying build/lib/molecule/test/resources/sample-collection/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/resources/sample-collection/molecule/default copying build/lib/molecule/test/resources/.yamllint -> build/bdist.linux-x86_64/wheel/./molecule/test/resources creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/overrride_driver creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/overrride_driver/molecule creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/overrride_driver/molecule/default copying build/lib/molecule/test/scenarios/overrride_driver/molecule/default/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/overrride_driver/molecule/default copying build/lib/molecule/test/scenarios/overrride_driver/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/overrride_driver/molecule/default creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/interpolation creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/interpolation/molecule creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/interpolation/molecule/default copying build/lib/molecule/test/scenarios/interpolation/molecule/default/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/interpolation/molecule/default copying build/lib/molecule/test/scenarios/interpolation/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/interpolation/molecule/default creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/cleanup creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/cleanup/molecule creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/cleanup/molecule/default copying build/lib/molecule/test/scenarios/cleanup/molecule/default/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/cleanup/molecule/default copying build/lib/molecule/test/scenarios/cleanup/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/cleanup/molecule/default creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/cleanup/molecule/default/tests copying build/lib/molecule/test/scenarios/cleanup/molecule/default/tests/test_cleanup.py -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/cleanup/molecule/default/tests copying build/lib/molecule/test/scenarios/cleanup/molecule/default/cleanup.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/cleanup/molecule/default creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/idempotence creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/idempotence/tasks copying build/lib/molecule/test/scenarios/idempotence/tasks/main.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/idempotence/tasks creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/idempotence/molecule creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/idempotence/molecule/raises copying build/lib/molecule/test/scenarios/idempotence/molecule/raises/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/idempotence/molecule/raises copying build/lib/molecule/test/scenarios/idempotence/molecule/raises/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/idempotence/molecule/raises creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/test_destroy_strategy creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/test_destroy_strategy/molecule creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/test_destroy_strategy/molecule/default copying build/lib/molecule/test/scenarios/test_destroy_strategy/molecule/default/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/test_destroy_strategy/molecule/default copying build/lib/molecule/test/scenarios/test_destroy_strategy/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/test_destroy_strategy/molecule/default creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/test_destroy_strategy/molecule/default/tests copying build/lib/molecule/test/scenarios/test_destroy_strategy/molecule/default/tests/test_destroy_strategy.py -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/test_destroy_strategy/molecule/default/tests creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/driver creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1 creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default copying build/lib/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default copying build/lib/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default copying build/lib/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default/destroy.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default copying build/lib/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default/create.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/meta copying build/lib/molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/meta/main.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/meta creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/driver/delegated creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/driver/delegated/molecule creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/driver/delegated/molecule/default copying build/lib/molecule/test/scenarios/driver/delegated/molecule/default/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/driver/delegated/molecule/default copying build/lib/molecule/test/scenarios/driver/delegated/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/driver/delegated/molecule/default copying build/lib/molecule/test/scenarios/driver/delegated/molecule/default/destroy.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/driver/delegated/molecule/default copying build/lib/molecule/test/scenarios/driver/delegated/molecule/default/create.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/driver/delegated/molecule/default creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/driver/delegated/meta copying build/lib/molecule/test/scenarios/driver/delegated/meta/main.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/driver/delegated/meta copying build/lib/molecule/test/scenarios/.flake8 -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/verifier copying build/lib/molecule/test/scenarios/verifier/.pre-commit-config.yaml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/verifier creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/verifier/molecule creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/verifier/molecule/testinfra-pre-commit copying build/lib/molecule/test/scenarios/verifier/molecule/testinfra-pre-commit/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/verifier/molecule/testinfra-pre-commit copying build/lib/molecule/test/scenarios/verifier/molecule/testinfra-pre-commit/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/verifier/molecule/testinfra-pre-commit creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/verifier/molecule/testinfra-pre-commit/tests copying build/lib/molecule/test/scenarios/verifier/molecule/testinfra-pre-commit/tests/test_testinfra_pre_commit.py -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/verifier/molecule/testinfra-pre-commit/tests creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/verifier/molecule/testinfra creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/verifier/molecule/testinfra/shared copying build/lib/molecule/test/scenarios/verifier/molecule/testinfra/shared/test_shared.py -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/verifier/molecule/testinfra/shared copying build/lib/molecule/test/scenarios/verifier/molecule/testinfra/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/verifier/molecule/testinfra copying build/lib/molecule/test/scenarios/verifier/molecule/testinfra/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/verifier/molecule/testinfra creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/verifier/molecule/testinfra/tests copying build/lib/molecule/test/scenarios/verifier/molecule/testinfra/tests/test_testinfra.py -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/verifier/molecule/testinfra/tests creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/dependency creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/dependency/molecule creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/dependency/molecule/ansible-galaxy copying build/lib/molecule/test/scenarios/dependency/molecule/ansible-galaxy/requirements.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/dependency/molecule/ansible-galaxy copying build/lib/molecule/test/scenarios/dependency/molecule/ansible-galaxy/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/dependency/molecule/ansible-galaxy copying build/lib/molecule/test/scenarios/dependency/molecule/ansible-galaxy/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/dependency/molecule/ansible-galaxy creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/dependency/molecule/shell copying build/lib/molecule/test/scenarios/dependency/molecule/shell/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/dependency/molecule/shell copying build/lib/molecule/test/scenarios/dependency/molecule/shell/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/dependency/molecule/shell creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/side_effect creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/side_effect/molecule creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/side_effect/molecule/default copying build/lib/molecule/test/scenarios/side_effect/molecule/default/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/side_effect/molecule/default copying build/lib/molecule/test/scenarios/side_effect/molecule/default/side_effect.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/side_effect/molecule/default copying build/lib/molecule/test/scenarios/side_effect/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/side_effect/molecule/default creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/side_effect/molecule/default/tests copying build/lib/molecule/test/scenarios/side_effect/molecule/default/tests/test_side_effect.py -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/side_effect/molecule/default/tests creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/host_group_vars creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/host_group_vars/group_vars creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/host_group_vars/group_vars/example copying build/lib/molecule/test/scenarios/host_group_vars/group_vars/example/all.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/host_group_vars/group_vars/example creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/host_group_vars/host_vars copying build/lib/molecule/test/scenarios/host_group_vars/host_vars/extra-host -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/host_group_vars/host_vars creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/host_group_vars/host_vars/instance copying build/lib/molecule/test/scenarios/host_group_vars/host_vars/instance/all.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/host_group_vars/host_vars/instance copying build/lib/molecule/test/scenarios/host_group_vars/hosts -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/host_group_vars creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/host_group_vars/molecule creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/host_group_vars/molecule/links copying build/lib/molecule/test/scenarios/host_group_vars/molecule/links/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/host_group_vars/molecule/links copying build/lib/molecule/test/scenarios/host_group_vars/molecule/links/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/host_group_vars/molecule/links creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/host_group_vars/molecule/default creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/host_group_vars/molecule/default/group_vars creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/host_group_vars/molecule/default/group_vars/example copying build/lib/molecule/test/scenarios/host_group_vars/molecule/default/group_vars/example/all.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/host_group_vars/molecule/default/group_vars/example copying build/lib/molecule/test/scenarios/host_group_vars/molecule/default/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/host_group_vars/molecule/default copying build/lib/molecule/test/scenarios/host_group_vars/molecule/default/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/host_group_vars/molecule/default creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/host_group_vars/molecule/default/host_vars creating build/bdist.linux-x86_64/wheel/molecule/test/scenarios/host_group_vars/molecule/default/host_vars/instance copying build/lib/molecule/test/scenarios/host_group_vars/molecule/default/host_vars/instance/all.yml -> build/bdist.linux-x86_64/wheel/./molecule/test/scenarios/host_group_vars/molecule/default/host_vars/instance creating build/bdist.linux-x86_64/wheel/molecule/test/functional copying build/lib/molecule/test/functional/conftest.py -> build/bdist.linux-x86_64/wheel/./molecule/test/functional copying build/lib/molecule/test/functional/test_command.py -> build/bdist.linux-x86_64/wheel/./molecule/test/functional copying build/lib/molecule/test/functional/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test/functional copying build/lib/molecule/test/functional/.ansible-lint -> build/bdist.linux-x86_64/wheel/./molecule/test/functional copying build/lib/molecule/test/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/test copying build/lib/molecule/status.py -> build/bdist.linux-x86_64/wheel/./molecule creating build/bdist.linux-x86_64/wheel/molecule/driver copying build/lib/molecule/driver/delegated.py -> build/bdist.linux-x86_64/wheel/./molecule/driver copying build/lib/molecule/driver/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/driver copying build/lib/molecule/driver/base.py -> build/bdist.linux-x86_64/wheel/./molecule/driver copying build/lib/molecule/scenarios.py -> build/bdist.linux-x86_64/wheel/./molecule copying build/lib/molecule/interpolation.py -> build/bdist.linux-x86_64/wheel/./molecule creating build/bdist.linux-x86_64/wheel/molecule/lint copying build/lib/molecule/lint/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/lint copying build/lib/molecule/lint/base.py -> build/bdist.linux-x86_64/wheel/./molecule/lint creating build/bdist.linux-x86_64/wheel/molecule/verifier copying build/lib/molecule/verifier/ansible.py -> build/bdist.linux-x86_64/wheel/./molecule/verifier copying build/lib/molecule/verifier/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/verifier copying build/lib/molecule/verifier/testinfra.py -> build/bdist.linux-x86_64/wheel/./molecule/verifier copying build/lib/molecule/verifier/base.py -> build/bdist.linux-x86_64/wheel/./molecule/verifier copying build/lib/molecule/shell.py -> build/bdist.linux-x86_64/wheel/./molecule creating build/bdist.linux-x86_64/wheel/molecule/provisioner copying build/lib/molecule/provisioner/ansible_playbooks.py -> build/bdist.linux-x86_64/wheel/./molecule/provisioner copying build/lib/molecule/provisioner/ansible.py -> build/bdist.linux-x86_64/wheel/./molecule/provisioner copying build/lib/molecule/provisioner/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/provisioner copying build/lib/molecule/provisioner/base.py -> build/bdist.linux-x86_64/wheel/./molecule/provisioner copying build/lib/molecule/provisioner/ansible_playbook.py -> build/bdist.linux-x86_64/wheel/./molecule/provisioner copying build/lib/molecule/console.py -> build/bdist.linux-x86_64/wheel/./molecule copying build/lib/molecule/logger.py -> build/bdist.linux-x86_64/wheel/./molecule copying build/lib/molecule/__main__.py -> build/bdist.linux-x86_64/wheel/./molecule copying build/lib/molecule/config.py -> build/bdist.linux-x86_64/wheel/./molecule creating build/bdist.linux-x86_64/wheel/molecule/data copying build/lib/molecule/data/validate-dockerfile.yml -> build/bdist.linux-x86_64/wheel/./molecule/data copying build/lib/molecule/data/Dockerfile.j2 -> build/bdist.linux-x86_64/wheel/./molecule/data creating build/bdist.linux-x86_64/wheel/molecule/dependency copying build/lib/molecule/dependency/shell.py -> build/bdist.linux-x86_64/wheel/./molecule/dependency creating build/bdist.linux-x86_64/wheel/molecule/dependency/ansible_galaxy copying build/lib/molecule/dependency/ansible_galaxy/roles.py -> build/bdist.linux-x86_64/wheel/./molecule/dependency/ansible_galaxy copying build/lib/molecule/dependency/ansible_galaxy/collections.py -> build/bdist.linux-x86_64/wheel/./molecule/dependency/ansible_galaxy copying build/lib/molecule/dependency/ansible_galaxy/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/dependency/ansible_galaxy copying build/lib/molecule/dependency/ansible_galaxy/base.py -> build/bdist.linux-x86_64/wheel/./molecule/dependency/ansible_galaxy copying build/lib/molecule/dependency/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/dependency copying build/lib/molecule/dependency/base.py -> build/bdist.linux-x86_64/wheel/./molecule/dependency copying build/lib/molecule/constants.py -> build/bdist.linux-x86_64/wheel/./molecule copying build/lib/molecule/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule copying build/lib/molecule/scenario.py -> build/bdist.linux-x86_64/wheel/./molecule creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/scenario creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/scenario/driver creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/scenario/driver/delegated copying build/lib/molecule/cookiecutter/scenario/driver/delegated/cookiecutter.json -> build/bdist.linux-x86_64/wheel/./molecule/cookiecutter/scenario/driver/delegated creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}} creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} copying build/lib/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/INSTALL.rst -> build/bdist.linux-x86_64/wheel/./molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} copying build/lib/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/converge.yml -> build/bdist.linux-x86_64/wheel/./molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} copying build/lib/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/destroy.yml -> build/bdist.linux-x86_64/wheel/./molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} copying build/lib/molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/create.yml -> build/bdist.linux-x86_64/wheel/./molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/scenario/verifier creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/scenario/verifier/ansible copying build/lib/molecule/cookiecutter/scenario/verifier/ansible/cookiecutter.json -> build/bdist.linux-x86_64/wheel/./molecule/cookiecutter/scenario/verifier/ansible creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/scenario/verifier/ansible/{{cookiecutter.molecule_directory}} creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/scenario/verifier/ansible/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} copying build/lib/molecule/cookiecutter/scenario/verifier/ansible/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/verify.yml -> build/bdist.linux-x86_64/wheel/./molecule/cookiecutter/scenario/verifier/ansible/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/scenario/verifier/testinfra copying build/lib/molecule/cookiecutter/scenario/verifier/testinfra/cookiecutter.json -> build/bdist.linux-x86_64/wheel/./molecule/cookiecutter/scenario/verifier/testinfra creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}} creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/{{cookiecutter.verifier_directory}} copying build/lib/molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/{{cookiecutter.verifier_directory}}/conftest.py -> build/bdist.linux-x86_64/wheel/./molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/{{cookiecutter.verifier_directory}} copying build/lib/molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/{{cookiecutter.verifier_directory}}/test_default.py -> build/bdist.linux-x86_64/wheel/./molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/{{cookiecutter.verifier_directory}} creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/molecule copying build/lib/molecule/cookiecutter/molecule/cookiecutter.json -> build/bdist.linux-x86_64/wheel/./molecule/cookiecutter/molecule creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/molecule/{{cookiecutter.role_name}} creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/molecule/{{cookiecutter.role_name}}/{{cookiecutter.molecule_directory}} creating build/bdist.linux-x86_64/wheel/molecule/cookiecutter/molecule/{{cookiecutter.role_name}}/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} copying build/lib/molecule/cookiecutter/molecule/{{cookiecutter.role_name}}/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/molecule.yml -> build/bdist.linux-x86_64/wheel/./molecule/cookiecutter/molecule/{{cookiecutter.role_name}}/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}} copying build/lib/molecule/cookiecutter/molecule/{{cookiecutter.role_name}}/.yamllint -> build/bdist.linux-x86_64/wheel/./molecule/cookiecutter/molecule/{{cookiecutter.role_name}} creating build/bdist.linux-x86_64/wheel/molecule/command copying build/lib/molecule/command/drivers.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/reset.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/destroy.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/matrix.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/prepare.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/verify.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/list.py -> build/bdist.linux-x86_64/wheel/./molecule/command creating build/bdist.linux-x86_64/wheel/molecule/command/init copying build/lib/molecule/command/init/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/command/init copying build/lib/molecule/command/init/init.py -> build/bdist.linux-x86_64/wheel/./molecule/command/init copying build/lib/molecule/command/init/scenario.py -> build/bdist.linux-x86_64/wheel/./molecule/command/init copying build/lib/molecule/command/init/base.py -> build/bdist.linux-x86_64/wheel/./molecule/command/init copying build/lib/molecule/command/init/role.py -> build/bdist.linux-x86_64/wheel/./molecule/command/init copying build/lib/molecule/command/idempotence.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/lint.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/test.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/converge.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/check.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/side_effect.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/__init__.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/cleanup.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/login.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/syntax.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/dependency.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/base.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/command/create.py -> build/bdist.linux-x86_64/wheel/./molecule/command copying build/lib/molecule/util.py -> build/bdist.linux-x86_64/wheel/./molecule copying build/lib/molecule/api.py -> build/bdist.linux-x86_64/wheel/./molecule copying build/lib/molecule/platforms.py -> build/bdist.linux-x86_64/wheel/./molecule copying build/lib/molecule/py.typed -> build/bdist.linux-x86_64/wheel/./molecule copying build/lib/molecule/state.py -> build/bdist.linux-x86_64/wheel/./molecule running install_egg_info Copying src/molecule.egg-info to build/bdist.linux-x86_64/wheel/./molecule-4.0.1-py3.12.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/molecule-4.0.1.dist-info/WHEEL creating '/home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/.pyproject-builddir/pip-wheel-iwcb1hjt/.tmp-5w_vlrmz/molecule-4.0.1-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'molecule/__init__.py' adding 'molecule/__main__.py' adding 'molecule/api.py' adding 'molecule/app.py' adding 'molecule/config.py' adding 'molecule/console.py' adding 'molecule/constants.py' adding 'molecule/interpolation.py' adding 'molecule/logger.py' adding 'molecule/platforms.py' adding 'molecule/py.typed' adding 'molecule/scenario.py' adding 'molecule/scenarios.py' adding 'molecule/shell.py' adding 'molecule/state.py' adding 'molecule/status.py' adding 'molecule/text.py' adding 'molecule/util.py' adding 'molecule/command/__init__.py' adding 'molecule/command/base.py' adding 'molecule/command/check.py' adding 'molecule/command/cleanup.py' adding 'molecule/command/converge.py' adding 'molecule/command/create.py' adding 'molecule/command/dependency.py' adding 'molecule/command/destroy.py' adding 'molecule/command/drivers.py' adding 'molecule/command/idempotence.py' adding 'molecule/command/lint.py' adding 'molecule/command/list.py' adding 'molecule/command/login.py' adding 'molecule/command/matrix.py' adding 'molecule/command/prepare.py' adding 'molecule/command/reset.py' adding 'molecule/command/side_effect.py' adding 'molecule/command/syntax.py' adding 'molecule/command/test.py' adding 'molecule/command/verify.py' adding 'molecule/command/init/__init__.py' adding 'molecule/command/init/base.py' adding 'molecule/command/init/init.py' adding 'molecule/command/init/role.py' adding 'molecule/command/init/scenario.py' adding 'molecule/cookiecutter/molecule/cookiecutter.json' adding 'molecule/cookiecutter/molecule/{{cookiecutter.role_name}}/.yamllint' adding 'molecule/cookiecutter/molecule/{{cookiecutter.role_name}}/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/molecule.yml' adding 'molecule/cookiecutter/scenario/driver/delegated/cookiecutter.json' adding 'molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/INSTALL.rst' adding 'molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/converge.yml' adding 'molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/create.yml' adding 'molecule/cookiecutter/scenario/driver/delegated/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/destroy.yml' adding 'molecule/cookiecutter/scenario/verifier/ansible/cookiecutter.json' adding 'molecule/cookiecutter/scenario/verifier/ansible/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/verify.yml' adding 'molecule/cookiecutter/scenario/verifier/testinfra/cookiecutter.json' adding 'molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/{{cookiecutter.verifier_directory}}/conftest.py' adding 'molecule/cookiecutter/scenario/verifier/testinfra/{{cookiecutter.molecule_directory}}/{{cookiecutter.scenario_name}}/{{cookiecutter.verifier_directory}}/test_default.py' adding 'molecule/data/Dockerfile.j2' adding 'molecule/data/validate-dockerfile.yml' adding 'molecule/dependency/__init__.py' adding 'molecule/dependency/base.py' adding 'molecule/dependency/shell.py' adding 'molecule/dependency/ansible_galaxy/__init__.py' adding 'molecule/dependency/ansible_galaxy/base.py' adding 'molecule/dependency/ansible_galaxy/collections.py' adding 'molecule/dependency/ansible_galaxy/roles.py' adding 'molecule/driver/__init__.py' adding 'molecule/driver/base.py' adding 'molecule/driver/delegated.py' adding 'molecule/lint/__init__.py' adding 'molecule/lint/base.py' adding 'molecule/model/__init__.py' adding 'molecule/model/schema_v3.py' adding 'molecule/provisioner/__init__.py' adding 'molecule/provisioner/ansible.py' adding 'molecule/provisioner/ansible_playbook.py' adding 'molecule/provisioner/ansible_playbooks.py' adding 'molecule/provisioner/base.py' adding 'molecule/test/__init__.py' adding 'molecule/test/conftest.py' adding 'molecule/test/functional/.ansible-lint' adding 'molecule/test/functional/__init__.py' adding 'molecule/test/functional/conftest.py' adding 'molecule/test/functional/test_command.py' adding 'molecule/test/resources/.yamllint' adding 'molecule/test/resources/molecule.yml' adding 'molecule/test/resources/invalid_role_template/cookiecutter.json' adding 'molecule/test/resources/invalid_role_template/bad_format/README.md' adding 'molecule/test/resources/playbooks/delegated/create.yml' adding 'molecule/test/resources/playbooks/delegated/destroy.yml' adding 'molecule/test/resources/playbooks/delegated/inventory/group_vars/all/all.yml' adding 'molecule/test/resources/roles/molecule/meta/main.yml' adding 'molecule/test/resources/roles/molecule/tasks/main.yml' adding 'molecule/test/resources/sample-collection/galaxy.yml' adding 'molecule/test/resources/sample-collection/molecule/default/converge.yml' adding 'molecule/test/resources/sample-collection/molecule/default/molecule.yml' adding 'molecule/test/resources/sample-collection/roles/get_rich/tasks/main.yml' adding 'molecule/test/resources/templates/cookiecutter.json' adding 'molecule/test/resources/templates/{{cookiecutter.repo_name}}/template.yml' adding 'molecule/test/scenarios/.flake8' adding 'molecule/test/scenarios/cleanup/molecule/default/cleanup.yml' adding 'molecule/test/scenarios/cleanup/molecule/default/converge.yml' adding 'molecule/test/scenarios/cleanup/molecule/default/molecule.yml' adding 'molecule/test/scenarios/cleanup/molecule/default/tests/test_cleanup.py' adding 'molecule/test/scenarios/dependency/molecule/ansible-galaxy/converge.yml' adding 'molecule/test/scenarios/dependency/molecule/ansible-galaxy/molecule.yml' adding 'molecule/test/scenarios/dependency/molecule/ansible-galaxy/requirements.yml' adding 'molecule/test/scenarios/dependency/molecule/shell/converge.yml' adding 'molecule/test/scenarios/dependency/molecule/shell/molecule.yml' adding 'molecule/test/scenarios/driver/delegated/meta/main.yml' adding 'molecule/test/scenarios/driver/delegated/molecule/default/converge.yml' adding 'molecule/test/scenarios/driver/delegated/molecule/default/create.yml' adding 'molecule/test/scenarios/driver/delegated/molecule/default/destroy.yml' adding 'molecule/test/scenarios/driver/delegated/molecule/default/molecule.yml' adding 'molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/meta/main.yml' adding 'molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default/converge.yml' adding 'molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default/create.yml' adding 'molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default/destroy.yml' adding 'molecule/test/scenarios/driver/delegated_invalid_role_name_with_role_name_check_equals_to_1/molecule/default/molecule.yml' adding 'molecule/test/scenarios/host_group_vars/hosts' adding 'molecule/test/scenarios/host_group_vars/group_vars/example/all.yml' adding 'molecule/test/scenarios/host_group_vars/host_vars/extra-host' adding 'molecule/test/scenarios/host_group_vars/host_vars/instance/all.yml' adding 'molecule/test/scenarios/host_group_vars/molecule/default/converge.yml' adding 'molecule/test/scenarios/host_group_vars/molecule/default/molecule.yml' adding 'molecule/test/scenarios/host_group_vars/molecule/default/group_vars/example/all.yml' adding 'molecule/test/scenarios/host_group_vars/molecule/default/host_vars/instance/all.yml' adding 'molecule/test/scenarios/host_group_vars/molecule/links/converge.yml' adding 'molecule/test/scenarios/host_group_vars/molecule/links/molecule.yml' adding 'molecule/test/scenarios/idempotence/molecule/raises/converge.yml' adding 'molecule/test/scenarios/idempotence/molecule/raises/molecule.yml' adding 'molecule/test/scenarios/idempotence/tasks/main.yml' adding 'molecule/test/scenarios/interpolation/molecule/default/converge.yml' adding 'molecule/test/scenarios/interpolation/molecule/default/molecule.yml' adding 'molecule/test/scenarios/overrride_driver/molecule/default/converge.yml' adding 'molecule/test/scenarios/overrride_driver/molecule/default/molecule.yml' adding 'molecule/test/scenarios/side_effect/molecule/default/converge.yml' adding 'molecule/test/scenarios/side_effect/molecule/default/molecule.yml' adding 'molecule/test/scenarios/side_effect/molecule/default/side_effect.yml' adding 'molecule/test/scenarios/side_effect/molecule/default/tests/test_side_effect.py' adding 'molecule/test/scenarios/test_destroy_strategy/molecule/default/converge.yml' adding 'molecule/test/scenarios/test_destroy_strategy/molecule/default/molecule.yml' adding 'molecule/test/scenarios/test_destroy_strategy/molecule/default/tests/test_destroy_strategy.py' adding 'molecule/test/scenarios/verifier/.pre-commit-config.yaml' adding 'molecule/test/scenarios/verifier/molecule/testinfra/converge.yml' adding 'molecule/test/scenarios/verifier/molecule/testinfra/molecule.yml' adding 'molecule/test/scenarios/verifier/molecule/testinfra/shared/test_shared.py' adding 'molecule/test/scenarios/verifier/molecule/testinfra/tests/test_testinfra.py' adding 'molecule/test/scenarios/verifier/molecule/testinfra-pre-commit/converge.yml' adding 'molecule/test/scenarios/verifier/molecule/testinfra-pre-commit/molecule.yml' adding 'molecule/test/scenarios/verifier/molecule/testinfra-pre-commit/tests/test_testinfra_pre_commit.py' adding 'molecule/test/unit/__init__.py' adding 'molecule/test/unit/conftest.py' adding 'molecule/test/unit/test_api.py' adding 'molecule/test/unit/test_config.py' adding 'molecule/test/unit/test_interpolation.py' adding 'molecule/test/unit/test_logger.py' adding 'molecule/test/unit/test_platforms.py' adding 'molecule/test/unit/test_scenario.py' adding 'molecule/test/unit/test_scenarios.py' adding 'molecule/test/unit/test_scenarios_ordered.py' adding 'molecule/test/unit/test_shell.py' adding 'molecule/test/unit/test_state.py' adding 'molecule/test/unit/test_status.py' adding 'molecule/test/unit/test_text.py' adding 'molecule/test/unit/test_util.py' adding 'molecule/test/unit/command/__init__.py' adding 'molecule/test/unit/command/conftest.py' adding 'molecule/test/unit/command/test_base.py' adding 'molecule/test/unit/command/test_check.py' adding 'molecule/test/unit/command/test_cleanup.py' adding 'molecule/test/unit/command/test_converge.py' adding 'molecule/test/unit/command/test_create.py' adding 'molecule/test/unit/command/test_dependency.py' adding 'molecule/test/unit/command/test_destroy.py' adding 'molecule/test/unit/command/test_idempotence.py' adding 'molecule/test/unit/command/test_lint.py' adding 'molecule/test/unit/command/test_list.py' adding 'molecule/test/unit/command/test_login.py' adding 'molecule/test/unit/command/test_matrix.py' adding 'molecule/test/unit/command/test_prepare.py' adding 'molecule/test/unit/command/test_side_effect.py' adding 'molecule/test/unit/command/test_syntax.py' adding 'molecule/test/unit/command/test_test.py' adding 'molecule/test/unit/command/test_verify.py' adding 'molecule/test/unit/command/init/__init__.py' adding 'molecule/test/unit/command/init/test_role.py' adding 'molecule/test/unit/command/init/test_scenario.py' adding 'molecule/test/unit/cookiecutter/__init__.py' adding 'molecule/test/unit/cookiecutter/test_molecule.py' adding 'molecule/test/unit/dependency/__init__.py' adding 'molecule/test/unit/dependency/test_shell.py' adding 'molecule/test/unit/dependency/ansible_galaxy/__init__.py' adding 'molecule/test/unit/dependency/ansible_galaxy/test_collections.py' adding 'molecule/test/unit/dependency/ansible_galaxy/test_roles.py' adding 'molecule/test/unit/driver/__init__.py' adding 'molecule/test/unit/driver/test_delegated.py' adding 'molecule/test/unit/lint/__init__.py' adding 'molecule/test/unit/model/__init__.py' adding 'molecule/test/unit/model/v2/__init__.py' adding 'molecule/test/unit/model/v2/conftest.py' adding 'molecule/test/unit/model/v2/test_dependency_section.py' adding 'molecule/test/unit/model/v2/test_driver_section.py' adding 'molecule/test/unit/model/v2/test_platforms_section.py' adding 'molecule/test/unit/model/v2/test_pre_validate.py' adding 'molecule/test/unit/model/v2/test_provisioner_section.py' adding 'molecule/test/unit/model/v2/test_scenario_section.py' adding 'molecule/test/unit/model/v2/test_schema.py' adding 'molecule/test/unit/model/v2/test_verifier_section.py' adding 'molecule/test/unit/provisioner/__init__.py' adding 'molecule/test/unit/provisioner/test_ansible.py' adding 'molecule/test/unit/provisioner/test_ansible_playbook.py' adding 'molecule/test/unit/provisioner/test_ansible_playbooks.py' adding 'molecule/test/unit/verifier/__init__.py' adding 'molecule/test/unit/verifier/test_ansible.py' adding 'molecule/test/unit/verifier/test_testinfra.py' adding 'molecule/verifier/__init__.py' adding 'molecule/verifier/ansible.py' adding 'molecule/verifier/base.py' adding 'molecule/verifier/testinfra.py' adding 'molecule-4.0.1.dist-info/LICENSE' adding 'molecule-4.0.1.dist-info/METADATA' adding 'molecule-4.0.1.dist-info/WHEEL' adding 'molecule-4.0.1.dist-info/entry_points.txt' adding 'molecule-4.0.1.dist-info/top_level.txt' adding 'molecule-4.0.1.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Building wheel for molecule (pyproject.toml): finished with status 'done' Created wheel for molecule: filename=molecule-4.0.1-py3-none-any.whl size=248881 sha256=86b16c65db8cd97b2be31ffbb88fd0c36cc5b812e6622f76295281fd95d4cd9c Stored in directory: /home/pterjan/.cache/pip/wheels/aa/0a/55/d9aa2dd6e94f46013f9225bcc1cc07dbf2dc851a958fc718b0 Successfully built molecule + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.PvshmI + umask 022 + cd /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + '[' 1 -eq 1 ']' + '[' /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT '!=' / ']' + rm -rf /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT ++ dirname /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT + mkdir -p /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + mkdir /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd molecule-4.0.1 + '[' 1 -eq 1 ']' ++ ls /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/pyproject-wheeldir/molecule-4.0.1-py3-none-any.whl ++ xargs basename --multiple ++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/' + specifier=molecule==4.0.1 + '[' -z molecule==4.0.1 ']' + TMPDIR=/home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/.pyproject-builddir + /usr/bin/python3 -m pip install --root /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT --prefix /usr --no-deps --disable-pip-version-check --progress-bar off --verbose --ignore-installed --no-warn-script-location --no-index --no-cache-dir --find-links /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/pyproject-wheeldir molecule==4.0.1 Using pip 24.3.1 from /usr/lib/python3.12/site-packages/pip (python 3.12) Looking in links: /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/pyproject-wheeldir Processing ./pyproject-wheeldir/molecule-4.0.1-py3-none-any.whl Installing collected packages: molecule Creating /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/bin changing mode of /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/bin/molecule to 755 Successfully installed molecule-4.0.1 + '[' -d /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/bin ']' + '[' -z sP ']' + shebang_flags=-kasP + /usr/bin/python3 -B /usr/lib/rpm/redhat/pathfix.py -pni /usr/bin/python3 -kasP /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/bin/molecule /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/bin/molecule: updating + rm -rfv /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/bin/__pycache__ + rm -f /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1-4.mga10.noarch-pyproject-ghost-distinfo + site_dirs=() + '[' -d /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/lib/python3.12/site-packages ']' + site_dirs+=("/usr/lib/python3.12/site-packages") + '[' /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/lib64/python3.12/site-packages '!=' /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/lib/python3.12/site-packages ']' + '[' -d /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/lib64/python3.12/site-packages ']' + for site_dir in ${site_dirs[@]} + for distinfo in /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT$site_dir/*.dist-info + echo '%ghost /usr/lib/python3.12/site-packages/molecule-4.0.1.dist-info' + sed -i s/pip/rpm/ /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/lib/python3.12/site-packages/molecule-4.0.1.dist-info/INSTALLER + PYTHONPATH=/usr/lib/rpm/redhat + /usr/bin/python3 -B /usr/lib/rpm/redhat/pyproject_preprocess_record.py --buildroot /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT --record /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/lib/python3.12/site-packages/molecule-4.0.1.dist-info/RECORD --output /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1-4.mga10.noarch-pyproject-record + rm -fv /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/lib/python3.12/site-packages/molecule-4.0.1.dist-info/RECORD removed '/home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/lib/python3.12/site-packages/molecule-4.0.1.dist-info/RECORD' + rm -fv /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/lib/python3.12/site-packages/molecule-4.0.1.dist-info/REQUESTED removed '/home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/lib/python3.12/site-packages/molecule-4.0.1.dist-info/REQUESTED' ++ wc -l /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1-4.mga10.noarch-pyproject-ghost-distinfo ++ cut -f1 '-d ' + lines=1 + '[' 1 -ne 1 ']' + /usr/lib/rpm/check-buildroot + '[' -n '' ']' + /usr/share/spec-helper/clean_files + '[' -n '' ']' + /usr/share/spec-helper/compress_files .xz + '[' -n '' ']' + /usr/share/spec-helper/relink_symlinks + '[' -n '' ']' + /usr/share/spec-helper/clean_perl + '[' -n '' ']' + /usr/share/spec-helper/lib_symlinks + '[' -n '' ']' + /usr/share/spec-helper/gprintify + '[' -n '' ']' + /usr/share/spec-helper/fix_mo + '[' -n '' ']' + /usr/share/spec-helper/fix_pamd + '[' -n '' ']' + /usr/share/spec-helper/remove_info_dir + '[' -n '' ']' + /usr/share/spec-helper/fix_eol + '[' -n '' ']' + /usr/share/spec-helper/check_desktop_files + '[' -n '' ']' + /usr/share/spec-helper/check_elf_files + /usr/lib/rpm/brp-strip /usr/bin/strip + /usr/lib/rpm/brp-strip-comment-note /usr/bin/strip /usr/bin/objdump + /usr/lib/rpm/brp-strip-static-archive /usr/bin/strip + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/brp-remove-la-files + /usr/lib/rpm/redhat/brp-mangle-shebangs + env -u SOURCE_DATE_EPOCH /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j16 Bytecompiling .py files below /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/lib/python3.12 using python3.12 Not clamping source mtimes, $SOURCE_DATE_EPOCH not set + /usr/lib/rpm/redhat/brp-python-hardlink Processing files: molecule-4.0.1-4.mga10.noarch Executing(%doc): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.P9I6n1 + umask 022 + cd /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + cd molecule-4.0.1 + DOCDIR=/home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + export LC_ALL=C + LC_ALL=C + export DOCDIR + /usr/bin/mkdir -p /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + cp -pr /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/docs/_static /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + cp -pr /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/docs/ci.rst /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + cp -pr /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/docs/conf.py /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + cp -pr /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/docs/configuration.rst /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + cp -pr /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/docs/contributing.rst /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + cp -pr /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/docs/examples.rst /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + cp -pr /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/docs/faq.rst /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + cp -pr /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/docs/getting-started.rst /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + cp -pr /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/docs/index.rst /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + cp -pr /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/docs/installation.rst /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + cp -pr /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/docs/usage.rst /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + cp -pr /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/README.rst /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/doc/molecule + RPM_EC=0 ++ jobs -p + exit 0 Executing(%license): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.4HGA19 + umask 022 + cd /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + cd molecule-4.0.1 + LICENSEDIR=/home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/licenses/molecule + export LC_ALL=C + LC_ALL=C + export LICENSEDIR + /usr/bin/mkdir -p /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/licenses/molecule + cp -pr /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/molecule-4.0.1/LICENSE /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT/usr/share/licenses/molecule + RPM_EC=0 ++ jobs -p + exit 0 Provides: molecule = 4.0.1-4.mga10 python3.12dist(molecule) = 4.0.1 python3dist(molecule) = 4.0.1 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: python(abi) = 3.12 python3.12dist(ansible-compat) >= 2.2 python3.12dist(cerberus) > 1.3.4.0 python3.12dist(click) >= 8 python3.12dist(click-help-colors) >= 0.9 python3.12dist(cookiecutter) >= 1.7.3 python3.12dist(enrich) >= 1.2.7 python3.12dist(jinja2) >= 2.11.3 python3.12dist(packaging) python3.12dist(pluggy) >= 0.7.1 python3.12dist(pyyaml) >= 5.1 python3.12dist(rich) >= 9.5.1 Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build/BUILDROOT Wrote: /home/pterjan/rpmbuild/RPMS/noarch/molecule-4.0.1-4.mga10.noarch.rpm Executing(rmbuild): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.0Gj03w + umask 022 + cd /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + test -d /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + rm -rf /home/pterjan/rpmbuild/BUILD/molecule-4.0.1-build + RPM_EC=0 ++ jobs -p + exit 0 D: [iurt_root_command] Success!