Will using migration tool to upgrade to leap 16 retain all non-zypper (out of repo) apps

English Install/Boot/Login
1

I would like to verify that using the migration tool does not do a “new” install wherein any compiled non-zypper (out of repo) apps would be lost. I have many apps that I have compiled myself, independent of zypper, and I wish to retain them. I tried to do a migration tool – dry run to see what would happen but that does not show the files to be replaced.

Previous updates using releasever set to new value followed by zypper dup did not affect them. I realize that some apps might need to be recompiled to account for new versions of dependencies but thus has not been an issue.

If there is any doubt about keeping these intact, I would revert to old update method.

thanks, tom kosvic

2

What is “old update method”?

3

I call setting releasever to new version value and then running zypper dup the old method.

4

You can check for yourself that the migration tool does a quite elaborate repo switch, but in the end it does:

$DRYRUN zypper --releasever $TARGET_VER dup -y --force-resolution --allow-vendor-change --download-in-advance
            if [ $? -ne 0 ]; then # re-run zypper dup as interactive in case of failure in non-interactive mode
                $DRYRUN zypper --releasever $TARGET_VER dup --force-resolution --allow-vendor-change --download-in-advance

(from opensuse-migration-tool)
so that looks to me quite similar to “the old method”.

5

The migration tool performs the same actions as the “old update method” as you call it.

  • old repos get replaced by the new repos for the new release
  • 3rd party repos can be disabled (the tool asks)
  • a zypper dup is performed

It is meant to ease the upgrade process for inexperienced users, as it does the complete repo handling under the hood… But at the moment it confuses the inexperienced users…
And there are some bugs which are worked on.

So if you feel unsure about the new tool, simply perform the “old update method”. But be sure to read the wiki and the relase notes, as Leap 16 has a completely different repo structure (no backports, SLE and update repos).

6

So “install tool” does same as my “old method” and does not do a “fresh” install that would remove my old compiled apps.

Could I get pointed to the bugs of the migration tool that are being worked on? I don’t see any issues on git page.

thanks, tom kosvic

7

I only keep bringing my compiled apps up as, if they are deleted as would be in a fresh install, even recovering them from backups would be a very time consuming process. Pieces of them are everywhere.

thanks, tom kosvic

8
9

For me it silently removed the apcupsd daemon of my UPS. installed from the official repos at 15.x versions. had to add “hardware” repo manually to be able to reinstall it. also “nmap” was gone as non-oss repo was disabled. and today after a lot of updates this repo was disabled again. am curious what else will show vanished over time …

10

You’re right. The none-osd was deactivated again after today’s update. That really annoyed me. What’s the point of that?