I was just updating my system and got a concerning warning message that I’m not familiar with. A websearch didn’t yield an obvious answer.
Here is the error:
sudo zypper dup
[sudo] password for root:
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Building repository 'repo-non-oss' cache ...............................................................................................................................................................................................................................[done]
Error building the cache:
[openSUSE:repo-non-oss|http://cdn.opensuse.org/tumbleweed/repo/non-oss] Failed to cache repo (1).
History:
- 'repo2solv' '-o' '/var/cache/zypp/solv/openSUSE:repo-non-oss/solv' '-X' '/var/cache/zypp/raw/openSUSE:repo-non-oss'
/var/cache/zypp/raw/openSUSE:repo-non-oss/repodata/5605832130b78c8c6e0685d7e8d9f3bff412368daa73fa298e4c98bc4118781eab4c35834c69da8a816dc348f018fcbedd2789db978cc80803c1b298d336544f-primary.xml.zst: repo_rpmmd: Document is empty
at line 1:1
Command exited with status 1.
Warning: Skipping repository 'repo-non-oss' because of the above error.
Building repository 'repo-oss' cache ...................................................................................................................................................................................................................................[done]
Error building the cache:
[openSUSE:repo-oss|http://cdn.opensuse.org/tumbleweed/repo/oss] Failed to cache repo (1).
History:
- 'repo2solv' '-o' '/var/cache/zypp/solv/openSUSE:repo-oss/solv' '-X' '/var/cache/zypp/raw/openSUSE:repo-oss'
/var/cache/zypp/raw/openSUSE:repo-oss/repodata/7674d607ab3a57f5eed74a46b508d2b4b2a18bb06a37b775468e9587de2de8b2c1f4ef415ea109a03a32f2fc9f05ae360acf5552e125b4471e329f0bfbf20c5d-primary.xml.zst: repo_rpmmd: Document is empty
at line 1:1
Command exited with status 1.
Warning: Skipping repository 'repo-oss' because of the above error.
Some of the repositories have not been refreshed because of an error.
dist-upgrade: Due to the treatment of orphaned packages dist-upgrade depends on a proper
repository setup more than any other command. It must not continue if enabled repositories fail
to refresh. This may severely damage the system. If a failing repository is actually not needed,
it must be disabled. See 'man zypper' for more information about this command.
As an aside.
This does not tell us (and you) the most important element of a repo: where is it? In other words the URLs are missing.
Better next time do something like
I just tried again and the problem is persistent. It looks like it is more than the synchronizing. Can you or anyone else help make sense of the repos?
I think just checking for the mirrors fixed it. Because after running that command I used Discover, GUI approach to do the update and it was successful.
But just in case more action is needed, here is the results of that command you suggested:
sudo zypper -vvv dup
[sudo] password for root:
Verbosity: 3
Initializing Target
Refreshing service 'NVIDIA'.
Refreshing service 'openSUSE'.
Checking whether to refresh metadata for repo-non-free
Checking whether to refresh metadata for repo-non-oss
Checking whether to refresh metadata for repo-openh264
Checking whether to refresh metadata for repo-oss
Checking whether to refresh metadata for update-tumbleweed
Checking whether to refresh metadata for Packman
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...
Force resolution: No
Computing upgrade...
The following 13 package updates will NOT be installed:
ffmpeg-7
7.1.1-1699.9.pm.9 x86_64 Packman http://packman.links2linux.de
libavcodec61
7.1.1-1699.9.pm.9 x86_64 Packman http://packman.links2linux.de
libavdevice61
7.1.1-1699.9.pm.9 x86_64 Packman http://packman.links2linux.de
libavfilter10
7.1.1-1699.9.pm.9 x86_64 Packman http://packman.links2linux.de
libavformat61
7.1.1-1699.9.pm.9 x86_64 Packman http://packman.links2linux.de
libavutil59
7.1.1-1699.9.pm.9 x86_64 Packman http://packman.links2linux.de
libnvidia-egl-wayland1
1.1.19-49.7 x86_64 repo-non-free obs://build.suse.de/Proprietary:X11:Drivers
libOpenCL1
2.3.3-63.5 x86_64 repo-non-free obs://build.suse.de/Proprietary:X11:Drivers
libOpenCL1-32bit
2.3.3-63.3 x86_64 repo-non-free obs://build.suse.de/Proprietary:X11:Drivers
libpostproc58
7.1.1-1699.9.pm.9 x86_64 Packman http://packman.links2linux.de
libswresample5
7.1.1-1699.9.pm.9 x86_64 Packman http://packman.links2linux.de
libswscale8
7.1.1-1699.9.pm.9 x86_64 Packman http://packman.links2linux.de
libvdpau_nouveau
25.1.6-1699.421.pm.4 x86_64 Packman http://packman.links2linux.de
Nothing to do.
Discover occasionally generates a notification icon and my slight OCD tendencies mean I always click on it. I wasn’t aware that it shouldn’t be used. Thanks for the info.
OK. After release of Plasma6 I started testing Discover for the dup. If the solver does not find any issues it does the job fine, no difference with the compared zypper dup. In case it does, it will simply not execute the dup, but fail with a message.
I also tested dup with Myrlyn, and that does handle issues anddup, where YaST software manager cannot do the dup. The testing also resulted in the same as the zypper dup. So, it can be considered a GUI alternative, for users that prefer a GUI.