Hi, I know this is not the same thing as this topic, but just wondering how TumbleWeed → slowrole works? I have tried to find the build state for PHP on slowroll.
Slowroll takes its packages from Tumbleweed, so it should be updated shortly thereafter. Follow the Forums or the Factory mailin list, new snapshots for both Tumbleweed and Slowroll are reported there.
The supporting packages are not at the right versions for the slowroll version, so it fails to build…
Thanks, I think i found it, learning lots today ![]()
https://build.opensuse.org/package/show/openSUSE:Slowroll:Build:2/php8
Slowroll get’s a monthly distro-upgrade where it’s sync’d with a Tumbleweed snapshot about 5-7 days older than the most recent Tumbleweed snapshot. In between these distro-upgrades, regular interim package updates (security and otherwise) are provided.
So in-between the monthly update bumps, you don’t have to be concerned about new packages being added to your system or packages deemed obsolete being removed. All that is saved for the monthly major update bump.
Monthly update bumps are announced on the Slowroll subreddit by the Slowroll maintainer himself. Regular interim updates are announced here on the openSUSE forums.
Tumbleweed should always be updated using the command sudo zypper dup. In the same way, Slowroll monthly update bumps must be carried out using ‘sudo zypper dup’.
Although, you can use sudo zypper dup when doing interim updates for Slowroll, sudo zypper up will work as well. Personally, I track the updates, so I do zypper up for interim updates and then zypper dup when the monthly update bump to sync with Tumbleweed has been announced.
Why all this?
- Interim updates are significantly smaller in size than the typical tumbleweed snapshot. So this may be of benefit if bandwidth is important to you.
- There are anecdotal reductions in regression frequency with monthly distro-upgrades in Slowroll vs distro-upgrades 3-4 times per week on Tumbleweed. OTOH, if there is a regression in a Tumbleweed snapshot, this is typically quickly rectified in subsequent snapshots. Furthermore, it’s possible that one could be stuck with a regression lurking in a monthly Slowroll upgrade bump that’s not addressed until the next distro-upgrade a month later.
Some argue that if you dislike frequently updating Tumbleweed, then simply run distro-upgrades less frequently. Updating Tumbleweed weekly or even less frequently, is a common practice.
So, it all depends on preference. Both work well.
I have Tumbleweed on my laptop while I have Slowroll on my desktop.
While above is a correct explanation generally speaking, the original issue was a critical security update for PHP that is currently in some mirrors already for Tumbleweed (and will be on the others in the next few hours) but apparently does not build for Slowroll atm.
So if you have a publicly facing PHP server on Slowroll you may have to shut it down until the fix is available.
[This is one of the rare cases in which “Slowroll is still beta” applies]
Thanks, For now I have switched to tumbleweed,