Solus Updates

tresjam

This is not really a problem, it's just about understanding.

I keep a log about the kernel versions.

Sometimes I notice that sequential numbers (-182 etc.) are skipped, i.e. do not land on my computer via update.

On 06.08.2021 the kernel 5.13.8-191 was up to date. After that, I checked daily, there were no updates. Last time was the 20.08. at 21:00

Today on 21.08. at 07:30 an update is displayed, with the kernel 5.13.12-193.current.

Where was the -192 ?
In the changelog of the Software Center, the -192 is listed, for the 12.08.

I don't understand that. Does checking for updates sometimes not work? Or are the kernels sometimes not distributed/released via Solus?

WhiteWolf

tresjam it landed in unstable:
compare stable vs. unstable
https://pkgs.org/download/linux-current
and it's not skipped just latest kernel landed in stable skipping 192 from unstable as newer version was updated

kyrios

tresjam This is simply because a package can be updated multiple times on the unstable branch before a sync with the stable (shannon) branch is done.

It can be either because upstream released a new version before the sync, because the package had to be rebuilt because some libraries it uses have been updated and requires the dependencies to be rebuilt, because problems were found during the testing and the package had to be patched or rolled back.

Basically you can follow update of a package on the DevTracker i.e: here for linux-current. You can see on the 6th of august there was an update (before the friday sync), on the 12th there was another update (and there was no sync on the firday 13th so it's normal you didn't get that update) and then another update on Aug. 20th.

Another way to check this without having to go on the DevTracker is from the software center, search for the package you are interested in, then click on the Changelog tab and you'll see that you're not missing anything, even when several versions are installed at the same time.

kyrios

tresjam Quoting the first line of my previous response that answers your question

kyrios This is simply because a package can be updated multiple times on the unstable branch before a sync with the stable (shannon) branch is done.

tresjam

@kyrios this is what makes me confused. At the changelog tab in software center was a -192 but I've never seen it on my laptop ;-) It helps me to know that there could be updates which are not synced to the "public". It is like it is.