Since I failed miserable lately in upgrading my Leap 15.5 to Tumbleweed (SHIM issue) or upgrade to a higher Kernel 6.7 inside Leap via Backports (Freeze in Launch screen), I am seriously concerned about my data safety regards future mandatory upgrades to even a different architecture as it shall be with Leap 16 (change to ALP).
What will happen to my programs, which are not from Flatpak and their referenced data like coded paths? Will e.g. my Trillium notes still find its database?
My question may be very naive, sorry for that. I am just a bit concerned about Suse’ ability of migration between versions due to the above mentioned experiences.
ALP:
ALP: Adaptable Linux Platform.
Leap 16:
Leap 16 development hasn’t really started yet (15.6 is still in beta). I doubt anyone can give you a definitive answer yet.
2 Likes
The question might simply boil down to where you keep things. If everything is in your /home directory, there should not be any problems over migration. If things are in your / directory, then you may need to copy them to somewhere on your /home directory, save that and then copy them back to /. For example, I have quite a lot of mariadb data stored in /var which I simply copy to a suitable location in /home and then restore to mariadb after the fresh installation. I also copy the .bash_history file I have in /root to a suitable location in /home during such a move. This contains a record of all the important configuration changes I have made. I have been doing this for the past 17 years every time I acquired a new device and have yet to lose anything.
2 Likes