There is also https://bugzilla.opensuse.org/show_bug.cgi?id=1180316 - crash not compatible to kernel 5.10

My hope is that bsc#1180316 will be fixed by an upgrade to crash 7.2.9 I have plans to perform in the next week or two.

For the record, there is also, also https://bugzilla.suse.com/show_bug.cgi?id=1179970 which I plan to work on today.

Maintenance should become aware that both of these are a side-effect of publishing updated kernels without verifying they don't break crash. That's not a fault by maintenance but a lack of full consideration of the effect of the posted kernel update by the developers making them. That has been a repeated problem I have observed while maintaining crash and is essentially endemic to the nature of kernel/crash development as it stands. It usually requires a user to discover for us that kernel development has created a kernel that exceeds published crash capabilities.

Dominique Leuenberger (dimstar) - almost 4 years ago

reviewer

This is Tumbleweed - Maintenance is not involved

crash is indeed not taken into account to block a snapshot based on new kernels - so far it was never considered to be on the critical path of things. If needed, we can discuss that and leverage crash into the rings, with a working test suite in Stagingn as well. This in turn would require closer alignment with new kernel versions - in order to not block them for weeks.