Noob here. See below. Anyone know why these issues are happening? I just want to get some context on these issues.
PS: I chose #3 as recommended by Gemini. Why? Because YOLO!
advait@localhost:~> sudo zypper dup
[sudo] password for root:
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-11.0.2-Virt.1699.1104.5.x86_64 requires 'libxenctrl.so.4.22()(64bit)', but this requirement cannot be provided
not installable providers: xen-libs-4.22.0_02-Virt.1699.942.1.x86_64[Virtualization]
Solution 1: Following actions will be done:
install xen-libs-4.22.0_02-Virt.1699.942.1.x86_64 from vendor obs://build.opensuse.org/Virtualization
replacing xen-libs-4.21.1_06-2.2.x86_64 from vendor openSUSE
deinstallation of libvirt-daemon-driver-libxl-12.5.0-1.2.x86_64
deinstallation of kexec-tools-2.0.32+git15.g677dd2f-1.3.x86_64
deinstallation of libvirt-12.5.0-1.2.x86_64
Solution 2: install qemu-x86-11.0.2-1102.1.x86_64 from vendor obs://build.opensuse.org/home:ecsos
replacing qemu-x86-11.0.2-Virt.1699.1104.4.x86_64 from vendor obs://build.opensuse.org/Virtualization
Solution 3: keep obsolete qemu-x86-11.0.2-Virt.1699.1104.4.x86_64
Solution 4: break qemu-x86-11.0.2-Virt.1699.1104.5.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c):
May I suggest that, before you perform a Distribution Upgrade, the following command be executed –
# zypper refresh --force
The reason is possibly due to the fact that, Tumbleweed is a rolling release distribution and therefore, the repository metadata is often updated/corrected/changed …
In a worst case, after the Zypper forced “refresh”, you may also have to perform a
# rpmdb --rebuilddb
Followed by a 2nd Zypper “refresh” to pick up any previously unnoticed repository metadata changes …
Also, if Tumbleweed with SELinux activated then, after the Zypper “refresh” and before the Distribution Upgrade –
The refresh step is completely unecessary when 3rd party repos are added correctly with the auto refresh flag. zypper dup automatically performs a refresh for repos with auto refresh flag enabled.
To explain a bit more, in your system there are (at least) a devel repo (Virtualization) and a /home: repo (/home:ecsos) enabled.
Packages in those repos might have versions not compatible with the versions in the default repos.
That usually happens because new versions are published to those repos as soon as they successfully build, while standard packages undergo testing in openQA before being published as part of a “snapshot” and so might take 1-2 days normally, or more if there are blocking problems, before a new version is made available for upgrade.
Occasionally packages in devel/home: repos might not build or might not be published for whatever reason and so might even lag the versions available in the standard repos.
All of the above applies to Packman as well.
So when you have such repos enabled on a system you as an admin must be aware of the implications and act accordingly.
A Linux geek friend helped me straighten out my repos. I learned a lot, but because I very rarely do Linux admin stuff or use the CLI beyond a few simple commands, the info may gradually leak out of my head.
