UEFI images currently fail on `bootctl install`:

  bootctl --path=/boot/efi install | Failed to get machine id: No medium found
  Action `Install UEFI bootloader` failed at stage Run, error: exit status 1

This is due to bootctl using the machine-id to set the default entry in
/boot/loader/loader.conf and the kernel postinst script using the same value to
create the matching /boot/loader/entries entry.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Avoid the warnings below when building the ospacks by using the noninteractive
frontend instead:

  debconf: unable to initialize frontend: Dialog
  debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 76.)
  debconf: falling back to frontend: Readline
  debconf: unable to initialize frontend: Readline
  debconf: (Can't locate Term/ReadLine.pm in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/Readline.pm line 7.)
  debconf: falling back to frontend: Teletype

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Sjoerd Simons authored 6 years ago and Frédéric Dalleau committed 6 years ago

Now that the sdk ospacks (and images) should build against next
re-enable everything again in Jenkins

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

Sjoerd Simons authored 6 years ago and Frédéric Dalleau committed 6 years ago

Update package names where appropriate and comment out packages not yet
available in the repositories. This allows a first round in building the
syysroot/devroot/sdk and basesdk ospacks.

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

The old GPLv2 version of coreutils shipped in our :target repository does not
ship the truncate applet.

Use the truncate tool provided by the (dockerized) host instead.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Sjoerd Simons authored 6 years ago and Emanuele Aina committed 6 years ago

/etc/machine-id is expected to either contain a UUID or be *empty*.
using echo doesn't result in an empty file, it generates a file with
just a newline.

Switch to using truncate so it's actually an empty file. Fixes systemd
being unhappy about the content.

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

Sjoerd Simons authored 6 years ago and Emanuele Aina committed 6 years ago

Make sure ospacks and images don't accidentally get build against 18.12

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

When virtualization is available, Debos uses systemd-nspawn to run commands in
the "chroot".

systemd-nspawn automatically takes care of setting up a working
/etc/resolv.conf, usually by bind mounting the "host" one:

 https://www.freedesktop.org/software/systemd/man/systemd-nspawn.html#--resolv-conf=

In our case, the host is the VM managed by fakemachine, which is configured to
use systemd-resolved.

The end result is that the stub /etc/resolv.conf pointing to 127.0.0.53 is
copied to our rootfs and included in the generated ospack.

This is arguably a weird corner of Debos, the resolv.conf file should really
not persist out of the chroot:

 https://phabricator.apertis.org/T4308



However, in the past ConnMan used to ship a tmpfiles.d snippet to overwrite
it with a link to /var/run/connman/resolv.conf but since commit 45ccde23a90c
shipped in ConnMan 1.36 the snippet has been changed to no longer overwrite
existing files, causing DNS resolution to fail on our images.

By dropping /etc/resolv.conf at the end of each recipe, after all the
chroot:true actions, we should be able to ensure that the final artifacts
don't ship it and at runtime the ConnMan tmpfiles.d snippet should work
 again as intended.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Subsume the unit mounting a tmpfs on /media that was formerly shipped by
apertis-customizations.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Add the /sbin/apertis-dev script that was shipped by apertis-customizations.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The apertis-customization package used to ship in tmpfiles.d/apertis.conf a
link from /etc/machine-id to /var/lib/dbus/machine-id to ensure that the
machine-id is unique.

This is now done automatically provided that /etc/machine-id is a empty file.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Subsume the apertis-create-homedir systemd unit creating $HOME at boot time
that was formerly shipped by apertis-customizations.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Store the submitted LAVA job ids in the output metadata for later processing.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Denis Pynkin authored 6 years ago and Denis Pynkin committed 6 years ago

Need to include `fsck` and `fsck.ext4` utils explicitly since there is
no image and partitioning during `ostree-commit` recipe to trigger the
default mechanism provided by `mkinitramfs` scripts.

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

Denis Pynkin authored 6 years ago and Denis Pynkin committed 6 years ago

Option 'flags' is not a part of mountpoints description.

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

Denis Pynkin authored 6 years ago and Denis Pynkin committed 6 years ago

Add options to kernel command line `fsck.mode=auto`
and `fsck.repair=yes` to allow file system check by initramfs script.

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

To reduce the number of moving parts during the Buster rebase we forced
the use of the 19.03 image-builder Docker container image.

Let's now move back to using the image-builder matching the current
release (still named `next` until we switch to the final name which
should be `v2019dev0`).

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Bulld the minimal ospack again by properly handling `null` debos arguments.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Speed things up and reduce resource consumption on a component that is
currently not a priority.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The multimedia demopack is intended for demonstrating contents in the HMI
music/video players, it is not needed on the headless minimal images and it
was erroneously introduced there with commit a1ebaae9.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

They got disabled during in the early phases of the Buster rebase, we should
start buidling them again now.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Sjoerd Simons authored 6 years ago and Emanuele Aina committed 6 years ago

With newer kernels it takes far longer in early boot to get random
numbers (as >= 4.18 kernels ensure good quality entropy is availble
before starting  providing randomness).

Install rng-tools to integrate with hardware random number generators
while jitterentropy-rngd can provide randomness without.

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

Signed-off-by: Andrej Shadura <andrew.shadura@collabora.co.uk>

Bring back the automatic check for production builds so that images are put in
their main location and test jobs are submitted to LAVA, but mangle the LAVA
webhook callback URL so that we don't create too much noise in Phabricator at
this point.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Due to a GPLv3/readline-releated issue gnupg2 is currently uninstallable and
thus ostree cannot be installed as well, breaking the image build.

In order to start playing with the LAVA setup while the ostree issue is being
resolved temporarily disable the failing images.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

The root filesystem was ro, with special sections marked as rw for the
old upgrade system. Now that we have ostree that's really quite
redundant.

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

I.mx6 is an important target but not the only arm target so drop the
various specialisations for it. The general images should be able to
boot on different SoC platforms as well

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

For the v2019dev0 release we'll move to assuming u-boot is in SPI flash
for i.mx6 which allows the sabrelite board to use standard images rather
then needing a specific ones.

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

The mktemp utility is now being shipped by coreutils, so the mktemp
package has to be removed before coreutils gets installed to avoid
file conflicts.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

APT's commit 806e94dcd "Set PATH=/usr/sbin:/usr/bin:/sbin:/bin when
running dpkg", released in 1.8.0_alpha3~1, causes Dpkg to not find the
copies of `rm` and `tar` we set aside in /usr/local/bin.

Signed-off-by: Emanuele Aina <emanuele.aina@collabora.com>

Starting ostree v.2018.7 (commit 9f48e212) the BLS specification has
been changed to 'ostree-$NUM-$OSNAME.conf'.

Signed-off-by: Denis Pynkin <denis.pynkin@collabora.com>

u-boot-menu provides similar functionality to our u-boot-common and is
available in debian, so prefer that

Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>

Only instantiated versions of the unit should ever run. So remove it
from the defualt target.

The root filesystem was ro, with special sections marked as rw for the
old upgrade system. Now that we have ostree that's really quite
redundant.