Bug#916670: cryptsetup doesn't work in buster

I have the same problem (though note that the configure script does in fact exit without an error despite printing the error to the console. I have to use dpkg-reconfigure to reproduce the error. I assume my system isn't bootable but I'm not eager to test this): root@tweedle:~# dpkg-reconfigure in

Kernel packages for 4.0.2 claim to be 4.0.0?

Just wondering but is it intentional that the kernel packages for 4.0.2 have /boot/vmlinuz-4.0.0-1-amd64 and modules in /lib/modules/4.0.0-1.amd64 ? I know there are circumstances where the Debian and upstream versions are intentionally distinct and, for example, sonames needn't match package vers

Bug#533574: closed by Bastian Blank (Re: Bug#533574: linux-image-2.6.29-2-686: Optoin CONFIG_ACPI_PROCFS_POWER is not set -- battery monitors don't work)

I don't think this is the right way to go about changing interfaces between packages in Debian. The correct way to go about this is to propose a new packaging policy that packages use the sysfs interface. When that's approved then issue bug reports against all packages using the old interface. Then