I have 15.4 and I’m happy but 15.5 is coming next month. I’m usually upgrade about a month later with zypper -dup
I have a bunch of other software that I got through opi. How will there apps be affected with the upgrade?
Thanks
Show us input/output from zypper lr -d and we can probably make intelligent suggestion(s).
$ zypper lr -d
# | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
---+-----------------------------+---------------------------------------------------------------------------------------------+---------+-----------+---------+----------+--------+-------------------------------------------------------------------------+--------
1 | openSUSE-Leap-15.4-1 | openSUSE-Leap-15.4-1 | No | ---- | ---- | 99 | rpm-md | hd:/?device=/dev/disk/by-id/dm-name-ventoy |
2 | packman | Packman | Yes | (r ) Yes | Yes | 90 | rpm-md | https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_15.4/ |
3 | repo-backports-debug-update | Update repository with updates for openSUSE Leap debuginfo packages from openSUSE Backports | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/update/leap/15.4/backports_debug/ |
4 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/backports/ |
5 | repo-debug | Debug Repository | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/15.4/repo/oss/ |
6 | repo-debug-non-oss | Debug Repository (Non-OSS) | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/distribution/leap/15.4/repo/non-oss/ |
7 | repo-debug-update | Update Repository (Debug) | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/15.4/oss/ |
8 | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/15.4/non-oss/ |
9 | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/non-oss/ |
10 | repo-oss | Main Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/distribution/leap/15.4/repo/oss/ |
11 | repo-sle-debug-update | Update repository with debuginfo for updates from SUSE Linux Enterprise 15 | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/debug/update/leap/15.4/sle/ |
12 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/sle/ |
13 | repo-source | Source Repository | No | ---- | ---- | 99 | NONE | http://download.opensuse.org/source/distribution/leap/15.4/repo/oss/ |
14 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/oss |
15 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/15.4/non-oss/ | Thanks
Except for #1, your original installation media, and Packman, a pseudo-standard, those are all standard repos. #1 should be removed, after which a zypper dup to 15.5 should be uneventful, as 15.5 is a relatively minor upgrade. I already have 20 15.5 installations, of which about 15 are zypper dups from 15.4 or 15.3.
You could check if all URLs have $releasever on the place of the release version. When that is the case, upgrade will be easier now and in the future because editing the repo files is not needed anymore. Easiest to see with
zypper --releasever CHECK lr -d
1 Like
Excellent news.
I have just removed the iso as part of the repos.
I’ll patiently wait for june.
Thanks
I just did it doesn’t show the release version just:
3 | repo-backports-update | Update repository of openSUSE Backports | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/leap/CHECK/backports/ | It just says CHECK.
Does this mean that it will switch from 15.4 to 15.5?
Thanks
Apparently you do not quite understand this. It is just a text replacement. Normally the current version (in this case 15.4) is replacing the $releaseverin the URL. During Upgrade you will use something like
zypper --releasever 15.5 ref
etc.
Then the $releasever will be replace by 15.5 and thus use the correct repos for the Upgrade. After the Upgrade finished, 15.5 will be used normally for following zypper actions.
Because it is a string replacement, you can use any string to replace $releasever. So I suggested CHECK.
When you now see the string CHECK in the place where you saw 15.4 in the first listing, that shows it is OK. So when you have this on all URLs that showed 15.4 in the first listing, it is in place on all repos And that is what you want.
You can use another word if you like:
zypper --releasever FOOBAR lr -d
The old way still works too. All my 15.x installations use exact copies of the very same .repo files I keep stored on my LAN server, e.g. this one:
# cat OSS.repo
[OSS]
autorefresh=1
baseurl=http://download.opensuse.org/distribution/leap/15.5/repo/oss/
enabled=1
keeppackages=0
name=OSS
path=/
type=rpm-md
Anyone still using literal versions in their repos need only do:
sudo sed -i 's/15.4/15.5/g' /etc/zypp/repos.d/*.repo
zypper ref
prior to running zypper dup to upgrade from 15.4 to 15.5. The ref following is only needed if one or more repos is not configured with autorefresh=1.
Of course the “old” way by editing the repo files still works. But hey, they offered us a nice feature, thus why not using it?
And all new installations do have it like that since some years already. I assume that not much people will take the trouble to remove the feature.