Apologies if this question is well-answered, but why isn't this package
holding back the kernel to 5.17? In my mind an "apt upgrade" should not
have pulled 5.18, especially when the net result may well be an unbootable
system. Surely there's some way to mark this package as broken in tandem
with 5.18?

I'm also quite surprised this wasn't caught in sid before it was pulled
into testing. Is there any form of testing for this package going on in sid?

Reply via email to