This is great! Only comment I have would be perhaps to note, in text, that 16.0 doesn’t have the update repositories, as a difference with 15.6, even though you illustrate it, just to make it more clear.
The Major Changes note about x86_64-v2 was important to me, as I usually do a test update on a netbook, circa 2009, before updating the desktop. The netbook is a Intel Core2 Solo U3500, which didn’t pass the “inxi -Cx | grep sse4_2” check. I guess it’ll stay Leap 15.6 or switch over to Tumbleweed.
OK, TW writes boot code to MBR on /dev/sda, while Leap used MBR /dev/sdb, both according to yast “Boot Loader”. I forced Leap to install boot code to /dev/sda in chroot.
But in Tw yast “Boot loader” still sees the the entry for 15.6 with kernel 6.4, this is why it is expecting this (no longer existing) kernel. But booting Leap worked once after zypper dup.
That’S why the repo-packages are blacklisted. no problem, but things apparently break without them. I’ve done several upgrades for leap and debian in the past, no problems at all.
No, they do not. It does not matter where repository definitions come from. But this topic becomes ridiculous as you continue to provide zero information beyond “it does not work” and mix different issues.
That IMNSHO is a pretty weird statement, the “paternalistic” makes it smell like a complot theory. Given the fact that you ignore part of a method that has worked on ~20 15.6 → 16.0 migrations, I cannot help you with the OP.
Passing through . . . for “dual boot” it is better to have one distro providing grub handling, rather than having grub installed on both systems??
I suggest turning off “osprober” on one of the systems, and then after upgrading a kernel on the “slave” distro, rebooting over to the “master” and run “sudo update-bootloader” . . . I then shut down and cold boot to get the newer kernel to show up.
Seems like you are adding complication, rather than using simplicity in your grub situation. If grub and osprober are installed in TW, you could try to rm grub from Leap 16 altogether . . . you could always add it in later?? At least try turning off osprober in one of the two . . . see how that goes.
Others here seem to have grub installed in every system and just let whatever happens happen, others have many distros running on one grub handler . . . right now I have 8 distros running across two drives handled by one grub/osprober . . . handled by TW.
I’d like to thank every one here who posted suggestions. The 15.6 → 16 upgrade of my 13 y.o. i7-3770 system went well following the instructions in the SBD. I disabled my Repo’s, added 3 new ones, and did the ‘dup’ instruction in terminal. Even though it took 5 hrs to finish on this old machine it seems to be working just fine. Unfortunately, my vBox doesn’t load, it is an issue with kext, I hopefully can get that going with an update from Oracle.
One hiccup I had after starting is that ‘Discover’, which I had never used before, had 31 security updates. I selected all and had a fail. The problem was with glibc 32bit binaries but when I updated them one-by-one they completed and then all the rest of the v16 security updates completed.
