GitLab

This makes sure we don't end up with broken images pulling newer
versions from Debian than we have.

This would ideally be checked in separate test step but until this is
there let's put it here rather than shipping broken images.

This commit adds support to build-image for building an additional boot
image containing U-boot and m4.bin.
This feature is enabled by the `want_boot_image` board config variable.

This makes sure it belongs to the user running the build process.  If we
create it during root.sh it will belong to root and not be writeable
later on when we want to indicate a tainted image.

Closes: #31

This will allow us to verify that the downloaded image uncompressed
correctly and to have a proper progress bare even with images of
different sizes.

We handle this via librem5-devkit-base to make the installer more slime
and have less cruft in the image builder.

This way we already create an initramfs which can later on be used by
flash-kernel.

Closes: #23

Otherwise it can be confusing.

Broken-by: c7f52db8

vmdebootstrap sometimes doesn't correctly evaluate the customize scripts
exit status. Make sure we don't accidentailly pass on failed image
builds by checking that the installation report is there as well.

We really want to switch to FAI at some point.

This allows us to modify it with versions fetched during build
that we don't know upfront.

This is mostly based on Angus Ainslie's work for the devkit test images.

Purple and experimental are "overlays" needing a base distribution.
Allow to specify them but to set a proper base distro in the
configuration.

CI is still enabled by default.

This needs

  Librem5/image-builder#8

to be really useful.

Closes: #9

Nobody is using them (although they were deemed important in Siegen) and they
only eat up build time.

Fix this error:

  ./build-image: line 96: [: missing `]'

This makes sure we don't try to fetch a u-boot on imx6 (nitrogen) where
we don't put a u-boot on the sdcard.

This allows us to use pam for PIN handling in phosh

u-boot needs a cortex M4 to load the DDR PHY training code so there
are no binary blobs in u-boot. This M4 binray lods that firmware

This moves the fdt_file configuration variable to the board file
with all of the other configuration variable

Now that we build different boards print out some variables upfront
so builds can be identified quicker.

so we can fit more tools into the image but still use a 4G card

In case of vmdeboostrap_opts use a shell array to indicate that we want
to expand.