Missing repository Rockstor Stable on 15.6

[phillxnet (Philip Guyton)]

@johnc Thanks for your patience on this front.

Re:

@johnc

My question is: is there any “harm” in updating the OpenSuse Leap 15.6 RPM’s on the OS side?

No.

@johnc

I didn’t want to affect my Stable 5.0.9.0 as I am putting this into production.

The 5.0.9-0 rpm was an earlier Release Candidate (RC4 as it goes) testing channel rpm:

V5.0+ Testing Channel Changelog

5.0.9-0 Released in testing channel updates on 19th April 2024 4th Stable Release Candidate (RC4) As usual: thanks to all those who have helped here on the forum, in GitHub issues (i.e. GitHub user ubenmackin’s estensive reporting/interactions re “Disk miss-attribution to ROOT”) and in side channel chats/support email. The main fixes here are hopefully the last remaining issues re our multiple Python updates within this single testing phase (now on Py3.11), a re-vamp/extensive clean-up/simpl…

It was the latest available Stable RC status rpm when we last rebuild our installers. But it is still pre-stable. This way we got folks off to a far newer start than having them run the older (and last available) 4.6.1-0 Stable rpm. And only the testing RC status rpms had fixes in that allowed us to use the newer Leap OSs.

@johnc

Also, I have been running 5.0.13-0 very successfully, …

Good, and yes, 5.0.13-0 is our RC8 Stable Release Candidate:

V5.0+ Testing Channel Changelog

5.0.13-0 Released in testing channel updates on 17th July 2024 8th Stable Release Candidate (RC8) As always: special thanks to @Flox co-maintainer, and @Hooverdan forum moderator & all-around core contributor. @Tex1954 thanks for the “unknown” scrub reporting: should be fixed now. We had a hick-up in btrfs-progs version sensing: now improved to be more robust. @Stevek thanks for reporting you findings re the Share resize: It related to an artifact of imported pool: but all good as we were…

@johnc

… I am putting this into production.

Then it is best to use the latest available RC status rpm: which today is 5.0.13-0 in testing: but this week I hope to also release 5.0.14-0 (RC9) into testing. You can then, as this version is only available in the testing channel to-date (as we are in late testing phase, hence the RC status), move your install over to the Stable channel to avoid accidentally running into the beginning of the next testing phase.

The hope is that 5.0.14-0 will, if no show-stoppers appear, then be promoted into the Stable channel, (new repo in 15.6), and we then kick-off the next testing phase.

So in-summary, use latest RC from testing, but then move back to Stable to halt the system at that version of the ‘rockstor’ rpm. Then when 5.0.14-0 (or what-ever is ear-marked as our first stable rpm in this latest run) is published in stable your system will just update to that, and all subsequent smaller fixes released to the stable channel.

Thank again for your patience and understanding here. I will soon begin working on a back-end to create an empty signed repo so we avoid these errors with the next release. But as-always time is always short and these repo errors, in zypper, are purely cosmetic; if also quite distracting. Plus we are now so close to the next Stable rpm that the repo can be created when that rpm is finally published.

We also plan, upon the first Stable release (which may be RC9, as above) to rebuild our installers so folks start out on our first released Stable rpm from the get-go (initial install). But again resources, human and otherwise, have held us back on that front. But as we develop, these restrictions are easing, especially as folks chip-in to support our efforts. Thanks again for your Stable subscription on that front.

Hope that helps.