Yep packaging was a nightmare. The fix for a bug in cron could require you to apply a kernel patch and reboot. But not if you had already applied a different kernel patch beforehand for some specific hardware, but which wasn't available except for particular hardware. But if you just install the patch it may succeed! But it didn't really apply, because the solver that figures out your patches ran separately and doesn't run fast enough to be part of the patch process but the patch has its own script that checks whatever separately to determine that. Oh and if you wait a week your process may break because the -20 version of the patch doesn't fix your problem anymore but it superceded the -12 version you were using anyway. But whichever one you apply, you'll have to reboot.

Like, to update cron. Even though through 3 versions of the same patch id, it does and does not fix cron.

Pure insanity with no product focus on user experience.