Migrating from OpenSUSE 15.6 to 16.0

That is not correct. If user uses 3rd party repos, the opensuse-migration-tool does not adapt them to a Leap 16.0 URL. The user is responsible to check all 3rd party URLs. Packman and h264 repos are an exception.

Utter nonsense…
The opensuse-migration-tool will not go away. It was developed for easier migration between different distribution flavors and easier upgrades of Leap versions.
And no, even IF the tool would go away, you don’t beed to reinstall via Agama as you can still simply perform the upgrade via zypper dup. Simply read the system upgrade wiki…

And Agama is only horrible if you do not spent some time to get used to its new features snd ways…

5 Likes

I had an issue running update-tool in my language, I solved using LANG=C opensuse-migration-tool --dry-run
I had also an issue with one of the laptops with nvidia but was double graphic card (VivoBook Pro N552VW Intel® Core TM i7 NVIDIA® GeForce® GTX TM 960m)
with the other laptops no issues with migration tool
but the best suggestion is BACKUP!!!

Thank you. Did you have to disable the nvidia repo before running the tool (and re-enable it afterwards) or did you keep it enable?

The migration tool takes care of Nvidia and Packman repos; other third party repos should be disabled and enabled again after the upgrade (with the possible exception of Chrome, cannot check ATM).

1 Like

in my case with the laptop with double graphic card nvidia and intel I didn’t succeed to upgrade, I installed 16.0 from usb with agama and had been a pain in the ass, and I have to thanks this forum for the help

Hi !

Will do the upgrade now. Backed up all my /home. Will use the migration tool and use the method described. Hope it won’t destroy my system, feel like the spaceship captain in “Event Horizon” movie about to press the button to reach the stars but went to hell.

Will create a new topic to mention all the issues encountered.

Me? I’d also have an “offline” install ISO (Leap 16) written to a USB flash drive, just in case the migration method does not work. :+1:

Could you please stop giving advice like this? I have now done ~20 installs, and it took a bit of extra attention, after my 25 years with the YaST installer, and none of your disasters happpened. FYI these were not just “use-full-disk” installs.
My habit with major releases always has beeen

  • backup /etc
  • backup /home/
  • perform a clean install with defaults as far as possible
  • add extra packages as per user needs
  • restore /home/
  • selectively restore /etc

Or, put differently: the installer is barely ever the problem, it mostly is the user making the wrong choices by assuming, not reading or not asking when in doubt.

Hi !

A good system should not let a user in limbo after an upgrade. Bad choices / missing prerequisites / incompatibilities should block any attempt.

I use the default recommendation (migration-tool) and I ended up in a non working system. Fortunately the AI is there but this should not happen

Hence the “dry run” …

I did. The dry-run did not detect any incompatibility.

Moreover, the dry-run did not detect any third-party repos. When I did it for real, it was detected that Packman, wine and Code were considered as third party repos and I had to disable them.

Then the problem is not with the distro. Please understand that it is, within reason, impossible to check all the thousands of repos + their content for potential issues/conflicts. The tool ( and whatever other upgrade methods ) are and should be aimed at upgrading the distro, not what the user has made out of it. Agreed?

Just checked and the migration tool “Dry Run” does detect third-party repos and offers to disable those not recognized by default, just pressing [OK].
So not sure what you actually did.

I don’t know if it is solved but I had a similar issue with dry-run

but solved with ‘LANG=C opensuse-migration-tool --dry-run’
did you used it?