On Sat, Oct 02, 2021 at 05:42:37PM +0200, Till Dörges wrote:
Hi Marcus, hi all,
thanks for your answer.
Am 02.10.21 um 09:11 schrieb Marcus Meissner:
I guess for *repo-backports-update* the policy is more or less that you ship what you (can) get from upstream.
No, it is the openSUSE Leap packages that are not in SLE, but made available to both PackageHub for SLE 15-sp3 and for Leap 15.3.
Sorry. Typo on my side. I meant repo-update-non-oss.
non-oss large has the non-free packages. obs ls openSUSE:Leap:15.3:NonFree To get the list. Opera and Steam get version updates out of those regulary.
Ack.
Looking at the release numbers I'm guessing that 0.6, 1.1 and 1.8 are from backports/PackageHub.
But only 1.8 is from repo-backports-update. Does this mean in addition to security updates that new versions of packages can be introduced via repo-backports-update?
Please note that "backports" is a project codename, but not the concept of the repository. Backports project is the non-SLE part of Leap 15.3 and packagehub. Its update policy is a bit less strict, so it can take updates via backported patches or by version updates. It is the same strategy we used for all previous Leap versions still.
It also generally seems that Leap 15.3 now offers more packages in multiple versions than previous versions. Is that correct?
By pure chance I would say (eg the rubygem-i18 example), not intentionally. Ciao, Marcus