Bugzilla – Bug 1192465
zypper dup fails to add repo-backports-update and repo-sle-update
Last modified: 2021-11-08 16:53:14 UTC
Tried "zypper dup" to 15.3 from working openSUSE Leap 15.2 with latest patches today. "zypper dup" installed the RPM openSUSE-release-15.3-lp1532.19.4 which is *missing* the update repo definitions for SLE and backports. IOW, after "zypper dup", which went fine, the system had only *one* update repo (repo-update) instead of three (repo-backports-update, repo-sle-update, repo-update). I'm ignoring repo-update-non-oss here. Doing a zypper in --oldpackage openSUSE-release-15.3-lp153.152.1 fixed the problem. # latest version of openSUSE-release leapbox:~ # rpm -ql openSUSE-release | grep repos leapbox:~ # rpm -qi openSUSE-release Name : openSUSE-release Version : 15.3 Release : lp1532.19.4 Architecture: x86_64 Install Date: Mon Nov 8 15:06:45 2021 Group : System/Fhs Size : 237868 License : BSD-3-Clause Signature : RSA/SHA256, Fri Nov 5 08:36:48 2021, Key ID b88b2fd43dbdc284 Source RPM : openSUSE-release-15.3-lp1532.19.4.src.rpm Build Date : Fri Nov 5 08:36:29 2021 Build Host : old-cirrus2 Relocations : (not relocatable) Packager : https://bugs.opensuse.org Vendor : openSUSE Summary : openSUSE Leap 15.3 Description : openSUSE Leap 15.3. Distribution: openSUSE Leap 15.3 # after downgrade leapbox:~ # zypper in --oldpackage openSUSE-release-15.3-lp153.152.1 leapbox:~ # rpm -ql openSUSE-release | grep repos /etc/zypp/repos.d/repo-backports-debug-update.repo /etc/zypp/repos.d/repo-backports-update.repo /etc/zypp/repos.d/repo-sle-debug-update.repo /etc/zypp/repos.d/repo-sle-update.repo
AFAICS the installer (YaST) was not even involved here (it was a "zypper dup"), so I don't see how this would be installer related.
I am not sure how much it can be expected to add those backports etc. repos again after a "zypper dup" for a real distribution upgrade.
See also https://doc.opensuse.org/documentation/leap/startup/html/book-startup/cha-update-osuse.html#sec-update-zypper I am not 100% sure, but I think this applies here as well: "Disable third-party repositories before starting the upgrade, or lower the priority of these repositories to make sure packages from the default system repositories will get preference. Enable them again after the upgrade and edit their version string to match the version number of the distribution of the upgraded now running system." IMHO those additional repos are considered "third-party repos" in this context. So AFAICS the expected procedure here is: - Disable those extra repos - Do the upgrade without them - Probably reboot into the new system. Not sure if it's absolutely required, but I would do that to play it safe. - Edit the repos so they match your new distribution version (URLs!) - Re-enable them and do another "zypper dup" with them; make sure to check carefully what it wants to do before you confirm those actions.
Apologies, if I chose the wrong component. IMHO this still is a severe bug (won't change the setting again, though) because it leaves the user with a system without the chance to get most security updates. But there's no warning, error or the like. It was working fine yesterday. The 15.2 system did not have any extra repos. Just the stock repo, repo-update etc. AFAICT the RPM openSUSE-release-15.3-lp1532.19.4 is simply broken (missing 4 files). So this bug has nothing to with the wrong repos being enabled when zypper dup was started.
As far as I can tell, this works as documented, so IMHO this bug can be closed with INVALID. Bug screening team, please have another look at this and close it accordingly if you agree.
Now I am confused. In the initial bug description, you wrote: > IOW, after "zypper dup", which went fine, the system had only *one* update repo (repo-update) instead of three (repo-backports-update, repo-sle-update, repo update). I'm ignoring repo-update-non-oss here. Those repos are not part of the regular distribution; they are add-on repos: - repo-backports-update - repo-sle-update I am aware that it may sound confusing; those repos also come from SUSE. Still, they are extra add-on repos; they need to be treated the same way as a repo by some openSUSE community member, i.e. as described above. There is no guarantee that all of those repos are available for the new distribution as well; there is also no guarantee that, if they are indeed available, they contain the same packages. This is where you have to take action. This is implicit in choosing the expert way of upgrading with "zypper dup". Using the YaST upgrade workflow would give you some more support for that, but still it's by no means 100% automated; you will probably have to take manual action as well if you have many extra repos. Packages may conflict. They may not be available for the new distro version. Some packages may have made it into the main line of the new distro version, so you may need to choose which one to use. All the things that are easy to automate we already tried to automate as much as possible; still, package dependency problems may appear. You have to check carefully if it does what you want it to do, even with a YaST upgrade. With a zypper upgrade (zypper dup), this involves even more manual steps.
There is also a bug when updating (no distribution update) to openSUSE-release-15.3-lp1532.19.4 This deletes: http://download.opensuse.org/update/leap/15.3/backports_debug/ http://download.opensuse.org/update/leap/15.3/backports/ http://download.opensuse.org/debug/update/leap/15.3/sle/ http://download.opensuse.org/update/leap/15.3/sle/ An: zypper in -f openSUSE-release-15.3-lp153.152.1 solves it..... Stephan
(In reply to Stephan Hemeier from comment #7) > There is also a bug when updating (no distribution update) to > > openSUSE-release-15.3-lp1532.19.4 > > This deletes: > http://download.opensuse.org/update/leap/15.3/backports_debug/ > http://download.opensuse.org/update/leap/15.3/backports/ > http://download.opensuse.org/debug/update/leap/15.3/sle/ > http://download.opensuse.org/update/leap/15.3/sle/ > > An: > zypper in -f openSUSE-release-15.3-lp153.152.1 > solves it..... Sounds like my bug is describing the same issue. It boils down to the fact that openSUSE-release-15.3-lp1532.19.4 is missing these 4 files. But the consequence is that you won't get (security) updates ...
It looks like bug my bug report effectively is a duplicate of bug 1192385. *** This bug has been marked as a duplicate of bug 1192385 ***
The problematic package is in the OSS Repo with date 20211105......