After a huge nightmare the past 2 days, which force me into an 18 hr nonstep session to recover my Leap 15.6 OS intact, including the repositories, I decided that the “zypper dup” command was insufficient and could end up in dangerous results (which happened to me as the results were literally scambled eggs, and key files such as libiff7.so deleted so that nothing would work, not zypper, not nmtui, nor anything else to recover from this massive disaster. I had to use the snapper command to drop back to my previous Leap 15.6 configuration, thank God ! for snapshots.
My simple question is this “will upgrading from Leap 15.6 to Leap 16.0” using the iso image dvd work and avoid disasters such as mine?
I need a clean and safe upgrade. Not a total scrambled eggs disaster which forced me to temporarily abandon the openSUSE service system on the repositories so that I could recover to a safe configuration. Thank God I was able to recover.
I currently have 10 16.0 installations. The first 8 were successful upgrades from 15.6 using zypper dup, 1 a successful upgrade from 15.6 using the migration tool, and one a fresh installation using Agama. #11 I prepared for on Friday with 15.5 as the starting point, currently at 15.6 after successful zypper dup, ready for zypper dup to 16.0, to be followed by 16.1 beta, also via zypper dup.
That does not sound good, but let me try to understand, so please correct if the story is different.
You did try a zypper dup from 15.6 to 16.0 and that led to a non-working system. You tried to recover the broken system but eventually realized that you could revert to an older snapshot an that still works. If you do the upgrade again you could immediately revert back to the older snapshot.
No, using a dvd to do the upgrade will probable not prevent disasters.
I see the openSUSE Migration Tool does Disable 3rd party repos prior to migration, not sure about the Distribution repositories. Try --dry-run first to preview planned changes.
I would also switch runlevel to runlevel 3 before doing the upgrade. Keep a watch on errors emitted during the upgrade process.
As you in fact do not communicate the complete command, nor what the configuration of repositories was at that moment in time, we can not comment much on this.
I did install the migration tool but I had third party repos enabled. I had to migrate from Leap 15.5 to Leap 15.6 and apparently that process was insufficient and led to further compounding problems on my supposed good Leap 15.6 OS into the Leap 16.0 transition
I have had to use btrfs tools to fix the mess and did a balance command which took about 3 hours to accomplish. I finally do have a good Leap 15.6 OS running now and the repos are in working order as well as the snapshot backups. I will try to use the migration tool again.
Just be aware that if your using third party repositories on the openSUSE Build Service request have gone out to delete 15.6 build targets and repositories…
One final question, running the “sudo zypper packages --orphaned” shows 119 packages sitting there and a lot are apparently Leap 16.0 packages. I am not going to touch them, as the current “zypper ref / up / dup / verify” commands execute safely. Is it okay to wait on this, until the actual Leap 16.0 upgrade? I have to change out my graphics card too, the Nvidia GeForce GT710 card is too old and I learned that it is NOT supported by Leap 16.0. Thank you for all your comments.
I carefully used Google’s Gemini Flash v3 to research these issues and was able to successfully remove any Leap 16.0 fragments from all of my 23 software repositories. I believe I have a clean working Leap 15.6 setup to be able to upgrade to Leap 16.0 using the migration tool. The openSUSE: service really caused problems as it partially installed software packages and rejected others, causing a scrambled eggs mixture of Leap 15.6 and Leap 16.0 files (and affecting zypper). This happened because the openservice add the $(basearch) variable to the URL lines for the repos ( and I didn’t know this) and a pull was only partially successful. I was forced to use the non-openSuse repositories to gain back control and fix this major mess. I believe now that the condition of my system will allow a successful migration from Leap 15.6 to Leap 16.0 using the migration tool.
I consider this topic closed. Thank you for your comments.