Looking at dependencies:

`$ repoquery --whatrequires ansible-runner` shows no results.

`$ repoquery --whatrequires python3-ansible-runner` shows:

ansible-runner-0:1.4.6-1.el8.noarch
ansible-runner-service-0:1.0.7-1.el8.noarch
ansible-runner-service-dev-0:1.0.7-1.el8.noarch
python-networking-ansible-0:5.0.1-0.20211101132217.b82d349.el8.src
python3-network-runner-0:0.2.2-2.el8.noarch
python3-networking-ansible-0:5.0.1-0.20211101132217.b82d349.el8.noarch

So it looks like it would be safe to drop the ansible-runner package within CentOS Virt SIG.

If needed we can cross tag python-ansible-runner-1.4.6-3.el8 into the SIG repo.

Il giorno mer 10 nov 2021 alle ore 10:41 Sandro Bonazzola <sbonazzo@redhat.com> ha scritto:

Hi,
in ovirt-4.5 repo we have ansible-runner-1.4.6-1.el8 which also provides python3-ansible-runner-1.4.6-1.el8.
But we are also consuming openstack-yoga repos and they are shipping python-ansible-runner-1.4.6-3.el8 but there's no ansible-runner package there.
This ends up with repository closure failure:
package: ansible-runner-1.4.6-1.el8.noarch from ovirt-master-centos-stream-ovirt45-testing
unresolved deps:
python3-ansible-runner = 1.4.6-1.el8

Do we need to maintain ansible-runner packaging in CentOS Virt SIG?
Should we rebuild ansible-runner with higher NVR?
+Martin Necas can you please look into this?

Thanks,
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV
Red Hat EMEA
sbonazzo@redhat.com
Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.

Sandro Bonazzola

MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV

Red Hat EMEA

sbonazzo@redhat.com

Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.