https://bugzilla.suse.com/show_bug.cgi?id=1201730 https://bugzilla.suse.com/show_bug.cgi?id=1201730#c3 Dan ��erm��k <dcermak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #3 from Dan ��erm��k <dcermak@suse.com> --- (In reply to Markus Zimmermann from comment #2)

(just saw that we have GCC in the package list, so i guess ruby-* vagrant-* is using GCC otherwise we wouldn't add it. For everything else we are using LLVM which hence is not an issue for this bug report)

In any case, let me know what i should try. I have two machines where i can reproduce this problem. The goal would be to install the official Vagrant package with LEAP 15.4. If we need additional repositories, that is fine for me. However, since this worked out of the box with 15.3, i see the whole report as a regression. Especially since the only way of getting this to work (at least so far) is to install the vagrant package of a specialized repository in a very specific combination. Would be great if the next users that want to try vagrant-libvirt do not run into this problem.

Sorry for taking so long to reply, but I cannot really support official vagrant package, because I have literally no way to contribute to it. The only thing that I can offer is trying to get a recent vagrant-libvirt to build in Virtualization:vagrant. -- You are receiving this mail because: You are on the CC list for the bug.