/boot seems too small now - 7.0 is 150 MB

[josch]

@ve7det

jsae@reform:~$ sudo reform-check

This looks okay.

@ve7det

it looks like I need to follow more detailed guides on cleaning out boot images with ‘pc’ and ‘rc’ status.

You should be purging linux-image-6.12.25-mnt-reform-arm64 as well as linux-image-6.14.5-mnt-reform-arm64 and linux-image-arm64, yes.

@ve7det

I appear to have 6.12.25 and 6.6.13 installed with some prerequisites blocking me from removing them. Even after apt full-upgrade.

The problem you see is not solved by installing newer packages. The problem is the other way round. The kernel images are so old that one of its prerequisites is too new and changed how it is intended to be invoked. Usually, this wouldn’t happen because you either use Debian stable (and then you are still running the old version of the package where it works) or you are using sudo apt full-upgrade which would’ve remove the old kernel version.

@ve7det

Purging configuration files for linux-image-6.12.25-mnt-reform-arm64 (6.12.25-1+reform20250503T130928Z)…
Usage: /usr/bin/linux-run-hooks image MAINT-SCRIPT KERNEL-VER IMAGE-PATH -- MAINT-PARAMS ...
       /usr/bin/linux-run-hooks headers MAINT-SCRIPT KERNEL-VER -- MAINT-PARAMS ...

To solve this error, edit this file as the superuser: /var/lib/dpkg/info/linux-image-6.12.25-mnt-reform-arm64.postrm and either replace the call to linux-run-hooks with a call to true or change linux-run-hooks postrm "$*" $version $image_path to linux-run-hooks image postrm $version $image_path -- "$@".

This issue was observed a year ago: 20250630 sudo apt update/full-upgrade with dpkg error - #6 by josch