On Mon, 2018-08-06 at 14:40 +0100, Ian Campbell wrote: > On Mon, 2018-08-06 at 21:15 +0800, Ben Hutchings wrote: > > > Inspecting the initramfs shows that the cryptsetup related parts are > > > missing for 4.17, but still in the 4.16 kernel. > > > > > > I was able to mitigate the issue by use the cryptsetup packages from > > > buster. > > > > This is strange. Kernel packages do not determine what goes into the > > initramfs. > > Possibly the cryptsetup package changed (and become broken). Then the > 4.17 initramfs was (re)built (due to the install/upgrade of that > kernel) while the 4.16 initramfs wasn't rebuilt.
In stable? (There's no backport of cryptsetup.) > I expected that there were be triggers in place which should have > caused the 4.16 initramfs (in fact, all initramfses) to be updated if a > relevant package (e.g. cryptsetup) was changed, but perhaps that was > more in hope than expectation and it's only an initramfs-tools update > which would trigger that? Installing or upgrading cryptsetup will trigger an update of the newest installed kernel version's initramfs. Ben. -- Ben Hutchings Larkinson's Law: All laws are basically false.
signature.asc
Description: This is a digitally signed message part
