Re: YaST on Leap 16!
"Carlos E. R." <[email protected]> Fri, 3 Jul 2026 22:46:29 +0200
| Newsgroups | gmane.linux.suse.general |
|---|---|
| Message-ID | <[email protected]> |
On 2026-07-03 22:10, Felix Miata wrote:
> James Knott composed on 2026-07-03 15:36 (UTC-0400):
>
>> Carlos E. R. wrote:
>>> You can do the migration with plain "zypper dup" plus some tweaks.
>> What would those tweaks be? As I mentioned, that migration tool did not
>> work.
> The simple version:
> Assuming that "old" laptop has CPU that supports 16.0:
> Disable non-standard repos
I disagree. Keep them, but to a minimum. In my case, without some extra
repos, the result crashes.
> Update standard repos (16.0 has no Update* repos)
> zypper dup
> Re-enable non-standard repos
> zypper up
> tweak: any non-standard repos' packages that dup was forced to switch to standard,
> while non-standard still needed
This is what I did with the best results of all my tests:
I manually edit the two extra repos so that the URLs are correct for
16.0 (I do not rely on "--releasever 16.0" much)
baseurl=http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_16.0/
baseurl=https://download.opensuse.org/repositories/X11:/Utilities/16.0/
Then I test.
*Eleanor:~ #* zypper clean
All repositories have been cleaned up.
*Eleanor:~ #* zypper --releasever 16.0 ref
...
This phase detects repos with wrong URL.
In my case, I needed the packman repo and the X11 repo. You may need
different. You find out when you enter "zypper dup" and see too many
packages that are going to be removed. Abort (before actually starting)
and find out where those missing packages live.
* Edit X11 and Packman repos URLs to 16.0
* In YaST, change network to network manager
* in YaST, remove wicked.
* install the tool (I will try to use the auxiliary scripts at the end
(/usr/share/opensuse-migration-tool/scripts/10_keepapparmor.sh,
/usr/share/opensuse-migration-tool/scripts/20_ia32.sh, and maybe
/usr/share/opensuse-migration-tool/scripts/20_pulse2pipewire.sh))
* install repository definitions directly (info obtained from
https://en.opensuse.org/SDB:System_upgrade):
o
sudo zypper --releasever 16.0 install openSUSE-repos-Leap
o
**sudo zypper lr
*
*Eleanor:~ #* zypper clean ; zypper --releasever 16.0 ref
*
*Eleanor:~ #* time zypper --releasever 16.0 dup --download-in-advance
*
Now, try the scripts.
/usr/share/opensuse-migration-tool/scripts/10_keepapparmor.sh <==
/usr/share/opensuse-migration-tool/scripts/10_keepselinux.sh <== choose one.
/usr/share/opensuse-migration-tool/scripts/20_ia32.sh
/usr/share/opensuse-migration-tool/scripts/20_pulse2pipewire.sh
For the full info, seek the post "[oS-EN] Testing
opensuse-migration-tool (report)" , May 6.
For instance, this paragraph:
Why are extra repos needed?
Because without them, there are orphaned packages.
The 15.6 test machine is a virtual machine under vmware player, very
simple, using desktop XFCE, and no repos besides the default
official ones. Then I added the packman repo with one multimedia
package, VLC, in order to test what would happen if I enable or
disable it.
But something like a dozen packages result orphaned and removed in
the upgraded machine, packages that were "official" in 15.6 and are
not in 16.0, belonging to XFCE. With the recommended practice of no
extra repos, the result is a broken 16.0 XFCE (no panel and no
menu). I had to add a new 16.0 repo, X11:utilities.
(Yes, a new fresh session would also work, I hope, but the
purpose of upgrading (instead of a fresh install) is having my
machine working as it was before the upgrade, less disruption)
So, if we disable repositories, we need an extra step after having
the repo list changed to 16.0: list the orphaned packages. List
them, then add the necessary repos so that the orphans become normal
packages. Repeat until no orphaned packages appear, or just the
expected ones (say, commercial apps).
How? This command produces the list.
|zypper packages --orphaned|
The YaST package manager (or myrlyn) shows them in a different colour.
--
Cheers / Saludos,
Carlos E. R.
(from openSUSE 16.0 (Laicolasse))
OpenPGP_signature.asc
(application/pgp-signature, 203 B)
-----BEGIN PGP SIGNATURE----- wmMEABEIACMWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCakgfpQUDAAAAAAAKCRC1MxgcbY1H1Tth AJ9BLnC+i9FJqvV5wCfAbVMxcNWz0wCdE0SX0cep8oHcJDkAhjc99xtFT40= =Da21 -----END PGP SIGNATURE-----