A day or so ago a major change was contributed to one of our most import SDB articles which is “The” Authority for doing an online upgrade
https://en.opensuse.org/SDB:System_upgrade
Testing the change, I have not been successful in getting the change to work, so am asking anyone with a little time to test this change in a virtual machine or install they don’t mind risking (although to date I haven’t yet destroyed a machine).
The Big Change…
Replacing the tried and true sed statement that converts all existing repo URLs and labels,
A new $releasever zypper option is used to supposedly write/change the version.
Documentation is sparse, says that this can be used as part of the upgrading process.
Bottom line, the following is supposed to replace the sed statement and change all release version numbers in the repo configuration files to 15.1 no matter what the current openSUSE version is
zypper --releasever 15.1 --gpg-auto-import-keys ref
But,
When I ran it in a 15.1 trying to change to 15.2 and when that failed to 15.0, in both cases the command failed and displayed the zypper help.
When I ran it in a 42.3 trying to upgrade to 15.1, the command ran successfully but when I did a “zypper lr -d” nothing had changed and when I checked the repo.d files directly, they also had not changed. Thinking that despite what was described in the MAN pages perhaps the modified strings were only in memory and not written to disk, I went ahead and tried a “zypper dup” but that resulted in the 42.3 suggesting it would re-install 42.3.
So, wondering what others might experience before I go ahead and revert the change back to how the SDB System Upgrade has worked for the past 6 or so openSUSE versions…
As always,
The first 3/4 of the SDB System Upgrade page can be skipped, those parts apply to people who are upgrading from 13.1 or earlier.
Start about 3/4 down the page with “Running the Upgrade” in big, bold headline type.
TIA,
TSU