openSUSE:Slowroll

Jump to: navigation, search

What

Logo of openSUSE Slowroll

Slowroll is a new experimental distribution from 2023 based on Tumbleweed, but rolling slower. With big updates once per month, and continous bug fixes and security fixes as they come in.

Slowroll-vs-tumbleweed-updates.svg


Use

For initial install, you can use the DVD iso from https://download.opensuse.org/slowroll/iso/?P=*DVD* or a VM image from https://download.opensuse.org/update/slowroll/images/ (note that cloud-init blocks root login with password by default).

Icon-warning.png
Warning: When migrating from Leap add the following repository:
root # zypper addrepo https://download.opensuse.org/slowroll/repo/oss/ leap-to-slowroll

Open a root session:

user $ su -

Then run all the following command at once:

root # shopt -s globstar && TMPSR=$(mktemp -d) && zypper --pkg-cache-dir=${TMPSR} download openSUSE-repos-Slowroll && zypper modifyrepo --all --disable && zypper install ${TMPSR}/**/openSUSE-repos-Slowroll*.rpm && zypper dist-upgrade

We do not recommend using development repos and packages on top, unless those are specifically compiled for Slowroll. Third party repositories which are not tested with Tumbleweed might break your installation.

Packman might work, but might also break occasionally. There is a special packman repository for Slowroll:

root # zypper ar --refresh -p 70 http://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Slowroll/Essentials/ packman

Like Tumbleweed, use zypper dup to upgrade.

All non default repositories will be disabled in the process.

Resources

Development

bmwiedemann did the design and scripting.

Development happens in https://build.opensuse.org/project/show/openSUSE:Slowroll and sub-projects with the use of https://github.com/openSUSE/slowroll-tools.

Untested packages go into https://build.opensuse.org/project/show/openSUSE:Slowroll:Build:1 or :2 first and are tested by openQA (TBD).

Most updates should be submitted to Factory and will auto-migrate into Slowroll after acceptance. Be sure to mention relevant CVE-fixes and boo# references in .changes files to speed up migration. If you know, you need a certain version of a dependency to build or run, add that to the .spec file, as packages could move at different speed compared to Tumbleweed.

Direct submissions should only be needed for backports of urgent fixes that require updated core packages in Factory (which are too risky to update quickly).