I think this one is unsatisfiable by design rather than a resolver glitch.
The current metadata in the repo:
Package: akrex-kernel
Version: 7.1.3-v8-16k+
Conflicts: linux-image, linux-image-rpi-v8, linux-image-rpi-2712, raspberrypi-kernel, clockworkpi-kernel
Package: clockworkpi-kernel
Version: 6.12.94-v8-16k+
Depends: akrex-kernel
So clockworkpi-kernel depends on the very package that declares a conflict with it. There is no state where both can be installed, and apt can only resolve it by removing clockworkpi-kernel — which is what produces the error message above.
The part I’d flag as more serious than the error itself: clockworkpi-kernel is typically the manually-installed package on existing systems. Once the conflict forces its removal, nothing depends on akrex-kernel anymore, so it gets marked as automatically installed. The next apt autoremove then removes it.
Because akrex-kernel owns /boot/firmware/kernel8.img, kernel_2712.img, all *.dtb and the entire overlays/ directory, dpkg deletes those from the FAT partition on removal. What’s left is only the GPU firmware (start*.elf, fixup*.dat, config.txt), so the firmware has no kernel to load and the device stops booting entirely — before the panel ever initialises, which is why there’s nothing on screen to diagnose.
I ran into exactly this and had to restore the boot partition offline from the .deb via a card reader. Looking at the reports in I killed my uConsole using apt, I suspect this is the same mechanism behind most of them.
Suggested fix: a transitional metapackage normally shouldn’t appear in Conflicts: at all — Replaces: plus Provides: is enough to take over the old package’s files and satisfy anything still referencing it. Dropping clockworkpi-kernel from the Conflicts: line should let it be replaced cleanly instead of removed.
Workaround for anyone affected in the meantime:
sudo apt-mark manual akrex-kernel
That keeps akrex-kernel anchored so autoremove won’t take it, regardless of what happens to the transitional package.