- Mar 06, 2019
-
-
/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>
-
Make sure ospacks and images don't accidentally get build against 18.12 Signed-off-by:
Sjoerd Simons <sjoerd.simons@collabora.co.uk>
-
- Mar 05, 2019
-
-
Emanuele Aina authored
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>
-
- Mar 04, 2019
-
-
Emanuele Aina authored
Subsume the unit mounting a tmpfs on /media that was formerly shipped by apertis-customizations. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
Emanuele Aina authored
Add the /sbin/apertis-dev script that was shipped by apertis-customizations. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
Emanuele Aina authored
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>
-
Emanuele Aina authored
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>
-
- Feb 20, 2019
-
-
Andrej Shadura authored
Signed-off-by:
Andrej Shadura <andrew.shadura@collabora.co.uk>
-
- Feb 18, 2019
-
-
Sjoerd Simons authored
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>
-
- Dec 12, 2018
-
-
Emanuele Aina authored
The `$arch-$platform` overlay mechanism was a relic of the old `cb_build` pipeline. Split it up into semantic overlays and include them only where appropriate. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
Emanuele Aina authored
The catch-all arch-platform overlay was a relic of the old `cb_build` pipeline. Split it up into semantic overlays and include them only where appropriate. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
- Nov 10, 2018
-
-
Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
Now that the ospack recipes have been split they can default to the correct type. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
Add the timestamp as `BUILD_ID` and the image type as `VARIANT_ID` in `/etc/os-release`, so at some point we'll be able to phase out `/etc/image_version`. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
- Nov 09, 2018
-
-
Andrej Shadura authored
Signed-off-by:
Andrej Shadura <andrew.shadura@collabora.co.uk>
-