Comment 0 for bug 1539157

Some architectures get "link_in_boot = yes" added to /etc/kernel-img.conf by lb_chroot_linux-image; it appears that cloud images built for these architectures (I have checked s390x and arm64) end up with an LZMA-compressed empty regular file at /boot/initrd.img (instead of the expected symlink to /boot/initrd.img-...).

In terms of time-of-introduction, I have confirmed that an s390x image built against proposed on the 12th of January was good, whereas an s390x image built against the main archive on the 25th was not.

(I suspect that this is actually an issue in something in the archive, but as I don't really know _what_, I have filed this against live-build for now.)