Migration problem from Leap 15.6 to Tumbleweed

English Install/Boot/Login
,
1

Good evening!

Faced with the choice of whether to upgrade from Leap 15.6 to Leap 16 or migrate to Tumbleweed, I thought I’d give Tumbleweed a go. (The reasoning being that an upgrade was needed either way, and I’d heard very good things about Tumbleweed.)

I tried to follow the instructions for online upgrade at https://en.opensuse.org/openSUSE:Migrate_Leap_to_Tumbleweed

Using the zypper dup command produced dozens and dozens of package conflicts, which I couldn’t possibly resolve competently. So I cancelled the upgrade at that point. The instructions hadn’t worked for me.

Upgrading from the desktop (now that the repos had been set to Tumbleweed as per the instructions) seemed to work. But after a system reboot, I have the following issues:

  • According to the boot loader and the KDE system settings, I’m still in Leap 15.6.
  • I can’t start any YaST modules, including the one to check and edit the boot loader. Error messages mention “Internal error (…)
    Details: cannot load such file – storage”.
  • Booting up the system no longer starts a KDE session automatically. But running “startx” after command line login brings back my desktop.

I can use the desktop and all the applications I’ve tried so far. But there’s obviously a problem.

Should I do a fresh install of Tumbleweed from the installation ISO or is there a less invasive way to fix this?

2

Hello and welcome to the openSUSE forums.

You tell a story, but we have not much information to see if you did things correct. E.g.

We then want to see that by zypper lr -d.

Also wen want be able to check your exact zypper dup .... command. And when you get dozens of package conflicts, you may post at least a few so we get some idea of what you see.

3

My advice is to install the opensuse-migration-tool using zypper an run that.

See also https://en.opensuse.org/SDB:System_upgrade

4

Thank you. I followed the instructions linked in my original post, so I had the impression that the repos were set up correctly:

# zypper lr -d
# | Alias        | Name         | Enabled | GPG Check | Refresh | Keep | Priority | Type   | URI                                                  | Service
--+--------------+--------------+---------+-----------+---------+------+----------+--------+------------------------------------------------------+--------
1 | repo-debug   | repo-debug   | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/debug   | 
2 | repo-non-oss | repo-non-oss | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss | 
3 | repo-oss     | repo-oss     | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss     | 
4 | repo-update  | repo-update  | Yes     | (r ) Yes  | Yes     | -    |   99     | rpm-md | http://download.opensuse.org/update/tumbleweed/      |

For the same reason, the dup command was exactly as specified in the linked instructions:
zypper cc -a && zypper ref && zypper dup --allow-vendor-change

Unfortunately, I can’t help with any specific package issues because I ran the command from a command line and didn’t know how to copy and paste from that. The issues were along the lines of libraries required by one package that couldn’t be provided by another. I didn’t recognise any of the names.

Thank you for pointing me towards the migration tool. I’ll try it.

5

Those two do look OK to me.

6

The migration tool seems to have done the job! I selected Tumbleweed as the target, waited for the upgrade to finish, rebooted the system, and as far as I can see everything is working again now.
I don’t know why the other method didn’t work, but the migration tool has worked. I’d recommend it to anyone trying to do this migration.

1 Like
7

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.