The path /usr/bin/virt-tail is correct, and the tool is invoked by the upstream code using that full path.

kubevirt-virt-launcher-1.1.0-1.1.x86_64 rpm is not supposed to be installed on the host system. It should be consumed only by the respective container image https://build.opensuse.org/package/view_file/Virtualization/virt-launcher-container/Dockerfile?expand=1. Considering that, can we just ignore the conflict? Or what the proper way of packaging the binary might be? I can install the binary into some weird location and then move it in the Dockerfile. But this looks more like an ugly hack.

Dominique Leuenberger (dimstar) - 6 months ago

reviewer

Ignoring is not an option - but you can declare the two packages as conflicting in the spec file using Conflicts:

---

Vasily Ulyanov (vulyanov) - 6 months ago

author source maintainer

Right, but I assume Conflicts: will need to be specified in both guestfs-tools and kubevirt-virt-launcher.

---

Dominique Leuenberger (dimstar) - 6 months ago

reviewer

one side declaring it is sufficient

---

Vasily Ulyanov (vulyanov) - 6 months ago

author source maintainer

Ah.. I thought it should be declared on both sides... Okay, will resubmit. Thx!