Hängt wohl davon ab, ob du ein Upgrade oder eine Neu-Installation machst.
Kann man immer noch installieren, sind im OSS Repo von Leap 16.0.
Denn ich lösche nach einem Upgrade immer alle Pakete, die als Systempakete gekennzeichnet sind, ich brauche kein Software-Leichen.
Code
stephan@linux64:~> zypper se -si yast2
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
S | Name | Type | Version | Arch | Repository
---+--------------------------+-------+--------------------------------------+--------+-----------
i | autoyast2-installation | Paket | 5.0.6-160000.2.2 | noarch | OSS
i+ | yast2 | Paket | 5.0.13-160000.2.2 | x86_64 | OSS
i | yast2-add-on | Paket | 4.7.0-160000.2.2 | noarch | OSS
i+ | yast2-bootloader | Paket | 5.0.21-160000.2.2 | x86_64 | OSS
i | yast2-buildtools | Paket | 5.0.2-160000.2.2 | noarch | OSS
i | yast2-core | Paket | 5.0.3-160000.2.2 | x86_64 | OSS
i+ | yast2-country | Paket | 5.0.3-160000.2.2 | x86_64 | OSS
i+ | yast2-country-data | Paket | 5.0.3-160000.2.2 | x86_64 | OSS
i+ | yast2-devtools | Paket | 5.0.2-160000.2.2 | noarch | OSS
i+ | yast2-firewall | Paket | 4.6.0-160000.2.2 | noarch | OSS
i | yast2-hardware-detection | Paket | 5.0.0-160000.2.2 | x86_64 | OSS
i+ | yast2-installation | Paket | 5.0.15-160000.2.2 | noarch | OSS
i | yast2-journal | Paket | 4.6.0-160000.2.2 | noarch | OSS
i | yast2-kdump | Paket | 4.7.2-160000.2.2 | x86_64 | OSS
i | yast2-ldap | Paket | 5.0.0-160000.2.2 | x86_64 | OSS
i+ | yast2-logs | Paket | 5.0.13-160000.2.2 | x86_64 | OSS
i+ | yast2-network | Paket | 5.0.5-160000.2.2 | noarch | OSS
i | yast2-ntp-client | Paket | 5.0.0-160000.2.2 | noarch | OSS
i | yast2-packager | Paket | 5.0.6-160000.2.2 | x86_64 | OSS
i | yast2-pam | Paket | 5.0.0-160000.2.2 | noarch | OSS
i | yast2-perl-bindings | Paket | 5.0.4-160000.2.2 | x86_64 | OSS
i+ | yast2-pkg-bindings | Paket | 5.0.5-160000.2.2 | x86_64 | OSS
i | yast2-proxy | Paket | 5.0.0-160000.2.2 | noarch | OSS
i | yast2-ruby-bindings | Paket | 5.0.4-160000.2.2 | x86_64 | OSS
i+ | yast2-security | Paket | 5.0.3-160000.2.2 | noarch | OSS
i | yast2-services-manager | Paket | 5.0.1-160000.2.2 | noarch | OSS
i | yast2-slp | Paket | 5.0.0-160000.2.2 | x86_64 | OSS
i+ | yast2-storage-ng | Paket | 5.0.34-160000.1.2 | x86_64 | OSS
i+ | yast2-theme | Paket | 5.0.1-160000.2.2 | noarch | OSS
i | yast2-trans-de | Paket | 84.87.20230818.ea489402e5-160000.2.2 | noarch | OSS
i | yast2-trans-stats | Paket | 2.19.0-160000.2.2 | noarch | OSS
i | yast2-transfer | Paket | 5.0.0-160000.2.2 | x86_64 | OSS
i | yast2-update | Paket | 5.0.1-160000.2.2 | x86_64 | OSS
i+ | yast2-users | Paket | 5.0.6-160000.2.2 | x86_64 | OSS
i | yast2-x11 | Paket | 5.0.2-160000.2.2 | x86_64 | OSS
i | yast2-xml | Paket | 5.0.0-160000.2.2 | x86_64 | OSS
i | yast2-ycp-ui-bindings | Paket | 5.0.1-160000.2.2 | x86_64 | OSS
Hinweis: Für eine erweiterte Suche inkl. nicht momentan aktivierter Remote-Ressourcen bitte
'zypper search-packages' verwenden.
stephan@linux64:~> 
