I’ve not upgraded yet from Leap 15.6 (ext4) to 16.0 on desktop PC.
To many private issues on this time, but also a little fear of proceeding failure as reported in many threads in this forum.
Here and from https://en.opensuse.org/SDB:System_upgrade I’ve learnt, there ist a (new) opensuse migration tool for helping users to upgrade system.
About this I’ve also red, there are some steps to do before starting the tool:
remove or deactivate non official repositories;
remove SLE, BACKPORT an update repositories, because these are there no more for Leap 16.0;
eventually remove or deactivate nvidia repository, if present (not my case);
Uninstall SELinux because possible issue on boot after upgrade.
Nevertheless I have some questions about the usage:
a) Uninstalling SELinux: which packages have to be selected for remove?
b) Are there further preparing steps to consider? Obviously backups …
c) Can you let activate non official repositories, which has an equivalent ones for Leap 16.0 before launching the migration tool?
d) What about packages, which has been installed in Leap 15.6 from non official repos?
Will they be automatically deleted or let installed?
e) Is the migration tool to be started in the console or is it a GUI application?
If not, it is needed to downgrade runlevel to no graphic mode?
f) Does the migration tool run well on dual boot systems? I mean, can you start other OS after upgrade?
g) What happens, if the upgrade process does not run well? Can you reboot the old Leap version to relaunch the migration tool?
g) Or it is maybe better installing Leap 16.0 as new (no upgrade)? More job due to reinstall many apps, but no questions about issues …
Sorry for the many questions, but I’ve not found detailed step to step information for the migration tool usage.
Yes. That is something most of us expect somebody to do before any more intricate action. This is so logical that most of us assume it is in everybody’s mind.
Nevertheless it misses completely in the pre upgrade steps noted by the TO. And also him asking what to do when something goes wrong gives a hint.
Thus you may not be the only one, but indeed there are too many who fall in the category “what can go wrong?”
Since we are late to the party and 15.6 didn’t receive updates after April 30, I would use the migration tool available for Tumbleweed here or that built by lkocman for 15.6 here, just in case something got fixed meanwhile.
Basically the migration tool adjusts repositories and performs a “zypper dup”, so the closer you are to a “standard” 15.6 the better chances you have.
Packman and Nvidia, and Chrome, repos are automatically adjusted, all others are automatically disabled and you may “switch packages to the official repos” first to ease migration.
Please make sure that your HW supports Leap 16 (x86_64_V2, Nvidia from Maxwell up) and possibly if you have exotic packages make sure they work with the 6.12 kernel etc.
Make a --dry-run before committing, to see if anything really bad is waiting for you.
And if anything really bad happens, you may still “Install fresh” afterwards, so I don’t think that your option g) is the first choice.
Always make sure you have a backup of everything precious on your system. Do not consider a separate homedir as such. Like @hcvv writes, it’s always assumed that people have proper backups, where many of them don’t. A system is something you can re-setup, your precious prvate photos / videos are lost when either software or hardware fails.
The hardware supports x86_64_V2 (checked in December).
The only very exotic application is DarGui (an old backup packages based on dar. Thus ist better, I make plain backups (/home + /Dokuments) bevor upgrading.
@ knurpht
Obviously backups will made.
It is also written in my opening (#1)
One thing which is often overlooked by the check-lists around major system upgrades is, the user’s Graphical User Interface.
The check-lists tend to concentrate on THE SYSTEM – everything close to the OS Kernel and, therefore relevant for Server upgrades.
What’s often not mentioned is, for Desktop systems, usually the user’s GUI is also upgraded to a new major version …
Once the system as such has been upgraded, each and every Desktop user will have the additional task to investigate how the GUI has changed – it’s settings and capabilities and user interactions and, and, and …
Often, each and every Desktop user will have to clean out their ‘~/.cache/’ directory – it’s usually a good idea to not remove the “fontconfig” directory located there because, “fc-cache -f -r” will need that directory – the system upgrade often supplies new system font descriptions which each Desktop user will need to refresh after the upgrade has completed.
)