You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Repos are being changed to use cdn.opensuse.org rather than download.opensuse.org. This is already in place for openSUSE Leap Micro 6.1, so most likely will be the case for openSUSE Leap 16.0 as well.
As of today, there's only one repository when you install the OS: https://cdn.opensuse.org/distribution/leap/16.0/repo/oss/. And while it is still early to tell how the repository tree will look like, keep in mind openSUSE Leap Micro 6.0 and 6.1 do not have a SLE-Updates repository anymore, so probably the same will happen for Leap 16.0. I can't tell for sure what will happen with updates, non-oss and non-oss-updates.
As part of the Hack Week 24 I started preparing the PRs to add openSUSE Leap 16.0.
As the time of creation of this card, 2024/11/20, openSUSE Leap 16.0 is still Alpha, so things can change.
Still, I thought it could be useful to document some things I discovered, so here we go:
Base platform
It is going to be SLFO, same already used for SUSE Linux Micro 6.1, openSUSE Leap Micro 6.1, and the same base to be used by SUSE Linux 16 as per https://news.opensuse.org/2024/10/07/leap-16-0-prealpha/
It is NOT going to be transactional.
Repos and packages
Repos are being changed to use
cdn.opensuse.orgrather thandownload.opensuse.org. This is already in place for openSUSE Leap Micro 6.1, so most likely will be the case for openSUSE Leap 16.0 as well.As of today, there's only one repository when you install the OS: https://cdn.opensuse.org/distribution/leap/16.0/repo/oss/. And while it is still early to tell how the repository tree will look like, keep in mind openSUSE Leap Micro 6.0 and 6.1 do not have a
SLE-Updatesrepository anymore, so probably the same will happen for Leap 16.0. I can't tell for sure what will happen withupdates,non-ossandnon-oss-updates.As of 2024/11/20 the repositories use the openSUSE Project GPG for signing, but the packages that come from SLFO are signed by a new key (see https://github.com/uyuni-project/uyuni/pull/9491/files).
Installer
No more YaST anymore, but agama. As of 2024/11/20 it's being discussed what to do for the systemconfiguration: https://code.opensuse.org/leap/features/issue/173
Therefore I guess no AutoYaST anymore? No explicit mention in the feature list or any announcement I could find.
Further resources
The text was updated successfully, but these errors were encountered: