This is extracted from Bug #2238787, where I faced of incompatibility between Systemtap / Kernel. I try to keep just the relevant comment. --- Additional comment from Vít Ondruch on 2023-09-15 16:04:07 CEST --- I can provide you just my POV as a packager of Ruby, who uses SystemTap just randomly to make sure the probes in Ruby works. And from this point of view: 1) SystemTap release announcements are completely invisible to me. 2) I am heavy distribution user and I think that the packages should works the best primarily in the context of the distribution and should provide the most convenience, therefore custom kernel build is not the scenario which would deserve too much focus. 3) I cannot judge if my use case is just niche scenario. However, it seems to me that `Recommends: kernel-headers >= 2.6.32 with kernel-headers <= 6.3.0-rc1` would provide nice default, while still keeping the flexibility of installing SystemTap withou kernel-headers, if required. But this is mostly me just thinking loud and it is partly OT for this ticket, therefore my apologies. After all, I am happy I have found working setup ;) --- Additional comment from Frank Ch. Eigler on 2023-09-15 17:00:20 CEST --- Making suggestions at the RPM level is an interesting idea. On the other hand, an rpm level version designation that would prevent a kernel from being upgraded to a version that is not designated as tested with systemtap could also lead to complaints. Not sure RPM can make it a default-warning that is still useful.