[Bug 1176044] New: Repository mess when upgrading
http://bugzilla.opensuse.org/show_bug.cgi?id=1176044 Bug ID: 1176044 Summary: Repository mess when upgrading Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: Ulrich.Windl@rz.uni-regensburg.de QA Contact: jsrain@suse.com Found By: --- Blocker: --- After upgrading Leap 15.1 to Leap 15.2 via "zypper dup" I had Packman and Nvidia repositories, and no pending online updates were displayed. Having a "specific feeling" I added the Nvidia and Packman repositories anew. The result was that I had two repositories named "Packman" and two repositories named "Nvidia" (I don't remember the exact names right now), where the URLs for each repository was different. So how could the typical user see that the repository being in use is for an older version of the OS? The more obvious question is when the upgrade method did not update those repositories also? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176044 http://bugzilla.opensuse.org/show_bug.cgi?id=1176044#c1 --- Comment #1 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- (I had been using the "Pro-Tipp" method from https://bugzilla.opensuse.org/show_bug.cgi?id=1174067#c9 for upgrading) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176044 http://bugzilla.opensuse.org/show_bug.cgi?id=1176044#c4 --- Comment #4 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- Zypper/Yast are not expected to do everything perfectly, but at least help to do so. Like asking before upgrade "There are community repositories ..." (maybe list them) "Should they be disabled (obsolete packages will be kept)?" "Should the packages they provide be removed (unless provided by other repositories)?" "Should I (zypper) try to update the URLs for those repositories, allowing to update the community packages as well?" Things like that. At least the user is alerted what the outcome of the upgrade will be most likely. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176044 http://bugzilla.opensuse.org/show_bug.cgi?id=1176044#c6 --- Comment #6 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- (In reply to Lukas Ocilka from comment #5)
This is how it looks like in Installer (Upgrade)
You missed the fact that I wasn't using YaST, but "zypper dup". -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176044 http://bugzilla.opensuse.org/show_bug.cgi?id=1176044#c8 --- Comment #8 from Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> --- (In reply to Ladislav Slezák from comment #7) ...
The correct solution for this issue is to use the "$releasever" variable in all repositories. That's actually already used even in 15.1, see
Ah! Now I understand what "--releasever 15.2" really did (and why it did not have any effect to some repositories) ;-) I had assumed zypper would use "much more magic" to update the repositories.
https://download.opensuse.org/YaST/Repos/_openSUSE_Leap_15.1_Default.xml .
-- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com