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

Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>

The chaiwala-apparmor-profiles contains some AppArmor abstractions in use in
some Apertis-specific profiles.

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

Emanuele Aina authored 6 years ago and Frédéric Dalleau committed 6 years ago

With this, running debos with no template parameters does not
fail badly:

    debos apertis-ospack-sysroot.yaml
    debos apertis-sysroot.yaml

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

Emanuele Aina authored 6 years ago and Frédéric Dalleau committed 6 years ago

The sysroots are specifically meant for actual cross-building and
debugging, so any runtime package can be dropped.

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

Emanuele Aina authored 6 years ago and Frédéric Dalleau committed 6 years ago

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

Emanuele Aina authored 6 years ago and Frédéric Dalleau committed 6 years ago

Move the shell commands to prepare the local ostree repository out of
the Jenkinsfile to a script for easier usage when building locally.

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>

The test ostree commit is generated after the successful commit.
Removing updatectl, it makes it impossible to mark an update successful.
Hence the bootcount will be increased at each boot, eventually causing
rollback to the previous deployment.

Ostree provides --skip-list that allows to create a commit with a list
of files to skip. That is useful to generate the rollback commit.
This way there is not need to modify existing recipes or provide
additional one. The execution time is also very short.

Signed-off-by: Frédéric Dalleau <frederic.dalleau@collabora.com>

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

Move the definition of env.PIPELINE_VERSION very early so that the devroot name
setting can make use of it.

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

The package has been introduced back into :sdk

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Dropped (obsolete) dependency on gir1.2-appindicator3-0.1 for blueman

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Ritesh Raj Sarraf authored 6 years ago and Ritesh Raj Sarraf committed 6 years ago

Extended Support Release of firefox browser with a long term support
plan. The same is also maintained in Debian Stable. The browser is part
of the :sdk component

Signed-off-by: Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>

Emanuele Aina authored 6 years ago and Frédéric Dalleau committed 6 years ago

Add a description field on the step installing the GPLv3 coreutils.

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

Emanuele Aina authored 6 years ago and Frédéric Dalleau committed 6 years ago

Pass multiple components to apt_source.sh when applicable and don't call it
with components that have been set up already like `target`.

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

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

Even after fixing https://github.com/systemd/systemd/issues/11925

 we
would still have issues by truncating the /etc/machine-id earlies, as
the actual problem is that the systemd-boot tools rely on it being set
for dual-boot scenarios:
* to avoid conflicts when creating entries, see the `90-loaderentry` kernel
  install trigger
* to set the entries for the currently booted installation as default in
  the loader.conf generated by `bootctl install`

In our image this is not useful, as the actual machine-id is supposed to be
uniquely generated on the first boot. However the impact is negligible, as
things still work albeit the code used to potentially disambiguate entries
doesn't match a real machine-id.

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

Jenkins is actually defining the full names for every artifact anyway and the
default is not particularly useful when building stuff locally without passing
any parameter so let's ensure the default names are sane and drop the
00000000.0 default.

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

Use a single parameter to speciffy the devroot to be downloaded and installed as
it is done for the mediapack.

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

Do like all the other artifacts and export the file listing.

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

The previous machine-id rework already moved one bit of ostree-prepare.sh
out of it, let's directly embed the two remaining commands in the
recipe directly for simplicity.

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

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

Target by default the apertis/v2019dev0/amd64-uefi/minimal OSTree branch
and not the lxc one, as that may be quite surprising when not explicitly
setting the board parameter.

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

When opening a new session sudo tries to resolve the fqdn of the host, but that
introduces a sensible delay if the host does not have a fqdn set up
appropriately, as it is often the case with development board or when booting
images in QEMU.

We currently also ship libnss-myhostname which in theory could solve the issue
at the system level and not just for sudo, but upstream configures it to come
*after* dns resolution to avoid breaking `hostname --fqdn`, see
https://github.com/systemd/systemd/issues/1280



Our use-case is sligthly different and we may configure libnss-myhostname to
precede dns resolution, but in the meantime keep disabling this in sudo as the
apertis-customization package used to do.

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

This file is required by recent libostree versions for several
operations like `ostree admin upgrade` to be sure we are booted in
ostree-based system. So just create this file in initramfs script
responsible for mounting ostree structure.

Check APERTIS-5762 for additional details.

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

Remove some packages that are meant for runtime development rather
than cross-building.

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

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

When deploying an OSTree commit /etc is not created. Trying to delete
files from a directory that does not exist is not the most advisable
action, so stop doing so.

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

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>