google-{oak,x64-cors,nyan*}: new initramfs too big

Describe your issue

What's the current behaviour?

bpo fails to build images for these devices with errors related to initramfs being too big, probably since !5000 (closed) was merged (which is known to be a bit bigger).

google-oak, google-x64-cors:

(002780) [06:25:26] (native) % dd if=/mnt/rootfs_google-x64cros/boot/vmlinuz.kpart of=/dev/installp1
dd: error writing '/dev/installp1': No space left on device

google-nyan-big, google-nyan-blaze:

==> Generating vmlinuz.kpart
Building depthcharge image for board 'HP Chromebook 14 G3' ('blaze').
Image with compression 'none' is too big for this board.
Couldn't build a small enough image for this board. This is usually solvable by making the initramfs smaller, check your OS's documentation on how to do so.

It's interesting that they give different errors. The second one sounds like we could use something stronger than 'none' as compression algorithm and possibly solve it that way? 🙂

If we can't fix it another way, I would make them depend on initramfs-minimal.

CC: @craftyguy, @calebccff, @jenneron, @adamthiede, @JustSoup321, @alpernebbi

How to reproduce your issue?

Run pmbootstrap install for these devices.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information