I have downloaded Leap 15.3 Offline Image. There are quite a few posts regarding problems not only in updating from 15.2 but also with fresh install. The problem as far as I could understand occurs in the course of applying updates. Is this so?
That is a little scary. I have been sticking to clean fresh installs till now. This time I was wondering if an upgrade would be a better idea. A fresh install entails setting up all the extras one has added and changes made. For example FreeCAD and LibreCAD, changing multimedia to Packman repo, problem with Eekboard files for Devnagri scripts and a number of other small settings have to be processed again. Since I have my working data files on a separate partition which is mounted independently, my worry is about the applications only. I can unmount this data partition, upgrade and mount it again. Any suggestions or remarks will be appreciated.
Is the problem in the installer? I was going through a dry run and got a message that the installer has been updated. If that was the fix it would be a comforting message.
Or should I wait a little longer till the issues are resolved.
Moving from a running release of openSUSE Leap to the next release of openSUSE Leap is an UPGRADE …
Within any given release, the packages related to that release are either patched or, updated
…
[HR][/HR]Please note that, an Upgrade is only successful when performed from the immediately preceding release of openSUSE – skipping releases is often the cause of an unsuccessful Upgrade …
An Upgrade from any given release of openSUSE to the next «relative to the previous
» release of openSUSE has a better than 99 % chance of success –
[INDENT=2]Upgrade from openSUSE version 13.2 to openSUSE Leap 42.1 …
Upgrade from openSUSE Leap 42.1 to openSUSE leap 42.2 …
…
Upgrade from openSUSE Leap 42.3 to openSUSE leap 15.0 …
…
Upgrade from openSUSE Leap 15.2 to openSUSE leap 15.3 …
[/INDENT]
If an On-Line Upgrade then, if unsure, initially only upgrade using the system repositories – upgrade the non-system repositories after the reboot …
If an Off-Line Upgrade then, even those who are unsure can usually successfully upgrade using both system and non-system repositories, provided that, care is taken …
After the Upgrade, always execute “rpmconfigcheck” and “rpm --verify --all” to find any needed configuration changes …
And about the urgency of upgrading. Again it depends on you. When you know there is something in 15.3 you really need ASAP, then of course you should go for ASAP.
When not, why hurry? I normaly wait at least a few months. Until somewhere halfway between the release of 15.3 and the enf-of-life of 15.2. Then all fuss about the new version has petered out. And there is time enough to have some mishap with the upgrade, because 15.2 will still be alive and kicking for some time.
> zypper lifecycle
Product end of support
Codestream: openSUSE Leap 15 2022-12-31
openSUSE Leap 15.2 2021-12-31
No packages with end of support different from product.
>
Thanks to you all for the information, suggestions and advice.
I have never upgraded earlier and have always done a fresh install. So at any given time I had two versions of the OS (on separate partitions of course). I was thinking of trying to upgrade from 15.2, but then considering the info in previous posts will hold on with 15.2 as it stands.
With 15.2 running I am in no hurry. And I can wait for sometime for 15.3 to settle down before I install it (fresh). Will keep track of the developments on the forum.
In earlier time I also reserved space on my systems, so I could install a new version (often jumping over one or more) in multi-boot to test it and make it ready for production. Since at least 15.0, I now do upgrades and did not really regret it. I admit that specially doing the first system here is always a bit tense.
And yes, I am not fond of going to any new version at all. I am a fan of the expression “never touch a running system”. It is only the threatening End-of-Life that forces me.
Maybe it matters what for you have a computer. I have it for several purposes, but still is the means for those purposes. So it should just do it’s humble work.
It is like a dust remover. It should remove dust and I am not really interested in it’s colour and if there is a new model, etc. But that is different of course when your hobby is “dust removers”
BTW, when you have again created your own frustrations, the people on the openSUSE forums most of the time will try to help you again. lol!
One reason to upgrade earlier rather than later has to do with how good your Internet connection is. My mother lives in a rural area and has a shared DSL line that can be hopelessly slow. I get her upgraded offline via the DVD, then she updates after re-enabling her repos. The longer we wait after release, the more updates there are. If we wait too long to upgrade, the amount of updates will get untenable.
For a smooth update with slow or unreliable connection first download everything and repeat until done:
**erlangen:~ #** **zypper dist-upgrade --download-only**
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...
The following 6 NEW packages are going to be installed:
ksysguardsystemstats-data ksystemstats5 ksystemstats5-lang layer-shell-qt5 libKSysGuardSystemStats1 libksysguard5-plugins
The following 11 packages are going to be REMOVED:
cpp9 gcc9 gcc9-c++ gcc9-fortran gcc9-info gcc9-locale libasan5 libksysguard5-helper libstdc++6-devel-gcc9 libstdc++6-pp-gcc9 libstdc++6-pp-gcc9-32bit
The following 180 packages are going to be upgraded:
NetworkManager-openconnect ...
...
systemsettings5 systemsettings5-lang tcsh tcsh-lang tigervnc units util-linux util-linux-lang util-linux-systemd xdg-desktop-portal-kde xdg-desktop-portal-kde-lang xembedsniproxy
xorg-x11-Xvnc xorg-x11-Xvnc-module
The following product is going to be upgraded:
openSUSE Tumbleweed 20210606-0 -> 20210609-0
180 packages to upgrade, 6 new, 11 to remove.
** Overall download size: 0 B. Already cached: 127.4 MiB. Download only. **
**Continue? [y/n/v/...? shows all options] (y): **
In cache libfreebl3-3.64-1.6.x86_64.rpm (1/186), 423.2 KiB (740.8 KiB unpacked)
In cache mozilla-nss-certs-3.64-1.6.x86_64.rpm (2/186), 279.8 KiB (505.4 KiB unpacked)
In cache libfreebl3-hmac-3.64-1.6.x86_64.rpm (3/186), 120.6 KiB ( 1.8 KiB unpacked)
...
In cache plasma5-desktop-lang-5.22.0-1.1.noarch.rpm (185/186), 4.5 MiB ( 12.2 MiB unpacked)
In cache plasma5-session-wayland-5.22.0-2.1.x86_64.rpm (186/186), 127.1 KiB ( 68.2 KiB unpacked)
**erlangen:~ #**
Then install from cached packages:
**erlangen:~ #** **time zypper dist-upgrade ****
Loading repository data... **
Reading installed packages...
...
[FONT=monospace] dracut: *** Creating image file '/boot/initrd-5.12.9-1-default' ***
dracut: *** Creating initramfs image file '/boot/initrd-5.12.9-1-default' done ***
Executing %posttrans scripts ...............................................................................................................................................................................................[done]
There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs.
real 1m59.012s
user 0m53.773s
sys 0m30.913s
**erlangen:~ #**[/FONT]
The above procedure warrants a fast and hasslefree install from cache.
Thanks, karlmistelberger. It’s a thought. Your post showed Tumbleweed, but she’s on Leap. I’ve thought about moving her (and me) to Tumbleweed, but haven’t yet.
I can try something like this on one of my machines and see how much needs to be downloaded. If it’s much over a couple of hundred MB, it won’t work very well. There are times where she’s lucky to get dial-up speeds.
I do like the upgrade from DVD method because it doesn’t upgrade a running system. The last several iterations have gone quite smoothly.
Several of my friends use Tumbleweed and have quarterly upgrades only. This works well form them and me, being called in case of trouble.
I can try something like this on one of my machines and see how much needs to be downloaded. If it’s much over a couple of hundred MB, it won’t work very well. There are times where she’s lucky to get dial-up speeds.
Avoid the rush hours. Upgrade in two steps. Filling up the cache may require multiple invocations of ‘zypper --download-only’. Don’t worry. The cache will fill up and zypper will report consistency: Overall download size: 0 B. Already cached: xxx.x MiB.
I do like the upgrade from DVD method because it doesn’t upgrade a running system. The last several iterations have gone quite smoothly.
With a slow and unreliable connection install or upgrade from the DVD iso is to be preferred over NET iso. Anyway you will want to have a backup system partition one of your machines, just in case something goes wrong. The backup considerably speeds up recover from mishap or disaster.
From the posts including yours in a few other threads it appears that that things are improving fast. A little more patience is all that is required from users like me.
Additional thanks to all those working on the issues.
I am back again. Posts re installation problems of LEAP 15.3 have nearly stopped. Repo issues appear to have been ironed out. So I will try to do a fresh install now. It will be alongside the existing 15.2.
One small doubt remains. I will be installing the 15.3 on the same SSD (reserved for OpenSUSE) as 15.2. Till now I was using the same/existing Swap partition (do not format) for the newer version. Considering the major changes in 15.3 should I continue to do so?
I see no problem. Swap space has no meaningful contents after shutdown and is freshly organised when taken into use (thus in most cases at boot). I am unsure if there is a “do no format” for swap at ll, and when there is I am not sure what it does.
There certainly used be such an option for Swap too. If formatted it gets a new identification and cannot be used by the previous existing version. I had run into that trouble some years back. My present doubt is due to closer alignment between Leap 15.3 and Suse SLES may impose some restrictions.
The quote should be “Swap space has no meaningful contents after shutdown”. When you only quote half of what people say you can accuse them of everything.
