Need input on update suggestions for "vagrant"

English Applications
1

Getting messages below from “sudo zypper patch”. For the last few days. Has not cleared. I have been using option 2.

I only know that vagrant is used in vm processes. I use a bunch of qemu/libvirt vms daily. I don’t want to corrupt these vms by picking wrong choice for vagrant.

Need some advice.

(base) tom@mydesktop: ~ $ sudo zypper patch
[sudo] password for root: 
Loading repository data...
Reading installed packages...
Resolving package dependencies...

Problem: 1: the installed ruby2.5-rubygem-vagrant_cloud-3.0.5-bp156.3.1.x86_64 requires 'rubygem(ruby:2.5.0:rexml:3.2) >= 3.2.5', but this requirement cannot be provided
 Solution 1: Following actions will be done:
  deinstallation of ruby2.5-rubygem-vagrant_cloud-3.0.5-bp156.3.1.x86_64
  deinstallation of vagrant-2.2.18-bp156.5.1.x86_64
  deinstallation of vagrant-bash-completion-2.2.18-bp156.5.1.noarch
  deinstallation of vagrant-emacs-2.2.18-bp156.5.1.noarch
  deinstallation of vagrant-libvirt-0.10.2-bp156.2.53.x86_64
  deinstallation of vagrant-vim-2.2.18-bp156.5.1.noarch
 Solution 2: do not install patch:openSUSE-2025-129-1.noarch
 Solution 3: break ruby2.5-rubygem-vagrant_cloud-3.0.5-bp156.3.1.x86_64 by ignoring some of its dependencies

Choose from above solutions by number or cancel [1/2/3/c/d/?] (c):
2

@tckosvic Vagrant changed their licensing and it was removed/dropped from openSUSE and not supported any more. I would let it remove them.

3

Upon suggestion from @malcolmlewis, I took option 1 – deinstallation.

Tested two qemu/libvirt vms and they still work.

thanks, tom kosvic