Skip to content

Commit c405ffd

Browse files
authored
Merge pull request #428 from lkocman/leap16_migration
Add Migrating to openSUSE Leap 16.0 article
2 parents f896356 + dbcafdd commit c405ffd

File tree

3 files changed

+96
-0
lines changed

3 files changed

+96
-0
lines changed
Lines changed: 96 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
1+
---
2+
author: Lubos Kocman
3+
date: 2025-10-01 16:00:00+02:00
4+
layout: post
5+
image: /wp-content/uploads/2025/10/opensuse-migration-tool.png
6+
license: CC-BY-SA-3.0
7+
title: Migrating to openSUSE Leap 16.0 with opensuse-migration-tool
8+
categories:
9+
- Announcements
10+
- openSUSE
11+
- Leap
12+
tags:
13+
- openSUSE
14+
- opensuse-migration-tool
15+
- Contribution
16+
- Community
17+
- Developers
18+
- Project
19+
- Linux
20+
- SLE
21+
- SUSE
22+
- Leap
23+
- Admins
24+
- Sysadmin
25+
- openssl
26+
- SELinux
27+
- Linux
28+
29+
---
30+
31+
Over the years, I have noticed that the biggest challenges during upgrades usually involve **3rd-party repositories**, mostly due to their unavailability for the new release or delays in catching up.
32+
33+
Another challenge has been **constant changes to distribution repositories**. For example, in Leap 15.3 we removed the ports repositories as part of the *Closing the Leap Gap* initiative and also introduced SLE Update repositories.
34+
35+
Now, with Leap 16.0, **update repositories are being removed entirely**. Leap Micro 6.X also no longer has dedicated update repositories.
36+
37+
In the past, users had to manually modify distribution repositories. Fortunately, [openSUSE-repos](https://github.com/openSUSE/openSUSE-repos) automates this process and puts distribution repositories under RPM management. This is now the default behavior for both **Leap Micro 6** and **Leap 16**. This dramatically simplified the whole upgrade and distribution migration process.
38+
39+
## Why use opensuse-migration-tool
40+
41+
Upgrading your system doesn’t have to be scary or complicated. The `opensuse-migration-tool` is designed to make the process **simple, safe, and predictable**. I got inspired by our [jeos-firstboot](https://github.com/openSUSE/jeos-firstboot), which uses dialog for smooth interactions. The tool also greets you with a **nice green dialog**, thanks to a customized dialogrc—giving it that familiar openSUSE look and feel right from the start.
42+
43+
Here’s what it can do for you:
44+
45+
1. Install updated distribution repository definitions automatically
46+
2. Disable non-distribution repositories to avoid conflicts
47+
3. Run `zypper dup` for a smooth, safe upgrade
48+
4. Offer post-upgrade scripts to adopt new defaults—or keep your preferred settings, for example AppArmor vs SELinux
49+
5. Perform pre-migration checks to make sure your system is ready, including verifying `x86_64-v2` support
50+
6. Reboot
51+
7. Optional snapper-rollback or simply boot to older snapshot from grub
52+
53+
The tool isn’t limited to just Leap n → Leap n+1. You can also upgrade to SUSE Linux Enterprise, Slowroll, or Tumbleweed. Slowroll → Tumbleweed upgrades work too, and recent requests include Leap Micro → Slowroll Micro. As long as it’s an upgrade, it will simply work.
54+
55+
Want to see it in action? Check out [LowTechLinux’s opensuse-migration-tool review on YouTube](https://www.youtube.com/watch?v=N-pKs8KJW48) for a hands-on demo and external validation.
56+
57+
## Getting started
58+
59+
In case the tool is not yet installed on your system do `sudo zypper in opensuse-migration-tool`
60+
61+
If you are using the tool for the first time or just want to check it out, run it in test mode:
62+
`/usr/sbin/opensuse-migration-tool --dry-run` # no need to use sudo in dry-run mode
63+
64+
This will not show exactly what will be upgraded, but it will give you a good idea of what the tool can do and it will not make any changes to your system.
65+
66+
Once you feel confident, run:
67+
`sudo opensuse-migration-tool`
68+
69+
The tool will offer to disable non-distribution repositories, which is strongly recommended. It will then trigger `zypper dup --r` and automatically rerun `zypper` if any issues occur.
70+
71+
The tool also performs pre-migration system checks. If you are affected by any issues, you might want to run the latest version directly from [git](https://github.com/openSUSE/opensuse-migration-tool). Contributions are welcome.
72+
73+
```
74+
git clone https://github.com/openSUSE/opensuse-migration-tool.git
75+
cd opensuse-migration-tool
76+
./opensuse-migration-tool --dry-run
77+
```
78+
79+
## Further documentation
80+
81+
More information can be found at [openSUSE System Upgrade](https://en.opensuse.org/SDB:System_upgrade). This document also suggests how to perform a manual upgrade to 16.0, although I would not recommend it, especially given the positive feedback we have received for the tool.
82+
83+
Make sure to read [Leap 16.0 release notes](https://doc.opensuse.org) as well as [Known bugs wiki](https://en.opensuse.org/openSUSE:Known_bugs_16.0) prior to upgrading.
84+
85+
## Future plans
86+
87+
I plan to provide an optional GTK4 interface that preserves the shared migration logic and power of Bash. This will use custom GTK4 dialogs to keep the openSUSE look and feel, but it will be invoked similarly to zenity. Here's a sneak peek from the first two dialogs:
88+
89+
<p align="center">
90+
<!--<img src="https://news.opensuse.org/wp-content/uploads/2025/10/opensuse-migration-tool-gtk.png" alt="opensuse-migration-tool-gtk" width="600">-->
91+
<img src="/wp-content/uploads/2025/10/opensuse-migration-tool-gtk4.png" alt="opensuse-migration-tool-gtk" width="600">
92+
</p>
93+
94+
95+
96+
<meta name="openSUSE, Open Source, development, Windows 10 end of support, Linux, secure operating systems, open source, Leap" content="HTML,CSS,XML,JavaScript">
35.7 KB
Loading
43.7 KB
Loading

0 commit comments

Comments
 (0)