pmbootstrap install --ondev: always build the image as it is done in bpo
We currently have two code paths, see this commit from !2082 (merged) for details:
install --ondev: no postmarketos-base-nofde (MR 2082) Install osk-sdl in the installer OS's boot partition for now. I forgot about a code path earlier, which could render an encrypted target OS without osk-sdl in the initramfs (and being unable to boot). The target OS gets embeded in the installer OS as image file. This can happen in two formats: a) a full image with partition header and the boot and root partition This is what bpo is doing when building the official, pre-built images, as this method allows having the exact same image available separately without the installer. Basically: pmbootstrap install \ --ondev \ --no-rootfs \ --cp path/to/rootfs:/var/lib/rootfs.img b) an image with just the root partition, no partition header and no boot partition. This is what you get when running regular "pmbootstrap install --ondev". It's slightly smaller, as there is no duplicate boot partition. If b) was done, the installer will copy the contents of the installer's boot partition to the target OS. And that means: if osk-sdl is missing from the installer's boot partition (the initramfs generated there), it will also be missing in the boot partition of the target OS! I think we should get rid of the b) code path to avoid confusion in the future/make maintenance. But until that is done, always install osk-sdl into the installer OS.
Let's get rid of the code path for b) in an elegant way.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information