What is the recommended method for tracking Kernel:stable on Leap these days?

Hi. Since I own and maintain a couple of out-of-tree device drivers, I use Kernel:stable for my Leap kernels so that I’m less likely to be blindsided by a bug report in the field should a user try to use the device with a Linux distribution that uses more recent kernels than Leap. TW has too much churn so this was a reasonable compromise for my workflow.

A while back, when 5.10 transitioned to 5.11, the upstream stable kernels introduced a GLIBC dependency that couldn’t be met on Leap 15.2 (see bugzilla 1182224). The outcome of that bug seemed to be that a new “backport” repository was set up for Leap users: Kernel:/stable:/Backport/standard. Its packages would not have the aforementioned GLIBC 2.33 dependency so they could be installed on Leap 15.2. That worked for a number of kernel 5.11.xx releases.

Fast forward to today and it seems Kernel:/stable:/Backport/standard has fallen out-of-sync. The most recent kernel offered there seems to be kernel-default-5.11.16 but the -syms, -devel, -macros and -docs packages found there have continued to track stable kernel releases and are up to 5.12.4 now.

Has this backports repository been deprecated since Leap 15.3 is imminent? Or has it been replaced by something else?

You know how to check build status on OBS, do not you? Kernel failed to build because

nothing provides dwarves >= 1.21, (got version 1.19-lp152.4.3.1)

Looks like someone needs to backport this package too.

Anyway, you need to either open bug report or at least post on openSUSE kernel mailing list. Kernel developers are not present on this forum.

I made my own Repo:
https://build.opensuse.org/project/show/home:Sauerland:branches:kernel-stable-backport