Zypper dup qemu update problem, various solutions, which one?

Tech newbie here. Running TW, Gnome, Wayland on an AMD Ryzen laptop. I ran sudo zypper dup this morning and got the following output describing a problem. See farther below. Which solution should I choose? Or should I just wait a few days until the TW devs fix the problem?

advait@localhost:~> sudo zypper dup
[sudo] password for root: 
Retrieving repository 'Packman Extras (Mesa)' metadata ...............................................................................................................................................[done]
Building repository 'Packman Extras (Mesa)' cache ....................................................................................................................................................[done]
Loading repository data...
Reading installed packages...
Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command.
Computing distribution upgrade...

Problem: 1: the to be installed qemu-x86-10.1.2-Virt.1699.1067.7.x86_64 requires 'libxenctrl.so.4.21()(64bit)', but this requirement cannot be provided
not installable providers: xen-libs-4.21.0_02-Virt.1699.928.1.x86_64[Virtualization]

 Solution 1: Following actions will be done:
  install xen-libs-4.21.0_02-Virt.1699.928.1.x86_64 from vendor obs://build.opensuse.org/Virtualization
    replacing xen-libs-4.20.2_02-1.1.x86_64 from vendor openSUSE
  deinstallation of libvirt-daemon-driver-libxl-11.9.0-1.1.x86_64
  deinstallation of kexec-tools-2.0.30-3.2.x86_64
  deinstallation of libvirt-11.9.0-1.1.x86_64
 Solution 2: install qemu-x86-10.1.2-1.1.x86_64 from vendor openSUSE
  replacing qemu-x86-10.1.2-Virt.1699.1067.6.x86_64 from vendor obs://build.opensuse.org/Virtualization
 Solution 3: keep obsolete qemu-x86-10.1.2-Virt.1699.1067.6.x86_64
 Solution 4: break qemu-x86-10.1.2-Virt.1699.1067.7.x86_64 by ignoring some of its dependencies

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

@invalid_user_name Hi, a self induced issue since your using a development repository… Your call, it may or may not resolve…

Problem fixed itself.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.