Comment # 10 on bug 1106751 from Dominique Leuenberger

(In reply to Fabian Vogt from comment #9)
> I can only think of a hacky way to (ab)use the rebuild bot: Add a fake
> "-rebuildme" subpackage to kernel-default-base.spec which has
> %(rpm -q --qf 'Requires: %{name} = %{version}-%{release}\n' kernel-default).
> 
> As the subpackage turns uninstallable once kernel-default changed, it would
> be rebuilt.
> 
> @dimstar, @lnussel: Any better idea?

Yucks - let alone this can't work (ignoring the non-escaped %{version} for
now):

The release counter is not under control on kernel-default-base: it is - and
will remain for a while, at 1.x, until it gets direct source changes, when it
turns into 2.x - and actually, weirdly, now it is 1.2.1.6... WTH)

So having a requires on a kernel version-release would only make it rebuild
forever in an attempt to reach the checking/rebuild counter of kernel-default

If anything, we'd need to add it to the parent/child rebuild trigger, as in:
https://github.com/openSUSE/openSUSE-release-tools/blob/master/rebuildpacs.pl#L77

But that is also 'just' a workaround - OBS itself has no support for this
(except switching to rebuild=direct|transitive, which is too expensive for TW)