- Mar 27, 2019
-
-
APERTIS-5675 This uses the new Recipe action to merged previous recipes in one. ROOTDIR needs to be reseted between ostree-commit and ostree-deploy Fixes: APERTIS-5739 Signed-off-by:
Frédéric Danis <frederic.danis@collabora.com>
-
- Mar 13, 2019
-
-
Emanuele Aina authored
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>
-
Emanuele Aina authored
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>
-
- Mar 08, 2019
-
-
Emanuele Aina authored
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>
-
- Mar 06, 2019
-
-
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>
-
- Feb 25, 2019
-
-
Option 'flags' is not a part of mountpoints description. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
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>
-
- Feb 15, 2019
-
-
Sjoerd Simons authored
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.
-
- Jan 30, 2019
-
-
Denis Pynkin authored
Now systemd UEFI boot stuff is available in separate package, so need to install it additionally. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
- Jan 28, 2019
-
-
Denis Pynkin authored
Do not need to install package `gimmiboot` since systemd-boot has support of EFI configurtion. Added kernel command line to `filesystem-deploy` action for proper generation of `/ets/kernel/cmdline` file. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
- Nov 15, 2018
-
-
The time to say goodbye to MD5 has come a long time ago. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
- Nov 10, 2018
-
-
Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
- Oct 04, 2018
-
-
Emanuele Aina authored
Once upon a time, when Apertis was still using live-build, scripts had to indicate in their extension if they had to be run in the chroot environment or outside of it. With Debos this is no longer needed, so drop the weird extensions that were cargo-culted in this repository. :) Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
- Sep 05, 2018
-
-
Emanuele Aina authored
The default demopack installs media files in `/home/shared`: by including them only in the ospack they are unavailble on the ostree images as the whole `/home` gets filtered out during `ostree commit`. Moving the extraction of the demopack when the full filesystem gets deployed to the images makes the media files available on ostree images as well. See https://phabricator.apertis.org/T5313 Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
Export the list of packages installed in the final artifact just before removing the dpkg database. This will allow to quickly check the artifacts contents without unpacking and processing them. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
Dump and store the list of files available on the images just before finalizing them, so developers do not need to run the images just to see what they ship. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
Make ospack and sysroot recipes take a generic basename for the output artifacts, to which the `.tar.gz` file extension is appended by the recipe itself. The recipes for the images already works this way as it works better when generating multiple artifacts. Signed-off-by:
Emanuele Aina <emanuele.aina@collabora.com>
-
- May 24, 2018
-
-
Sjoerd Simons authored
Now that we have a single 4.14 for all systems and linux-latest in apertis, install the kernel packages via the standard meta-packages rather then specific versions. Generally the debian meta for each architectures is linux-image-<debian architecture name>. Only armhf is a bit different as the standard kernel is armmp (arm multi-platform) so that needs special-casing. In ostree-commit also split out the u-boot-imx handling; that really shouldn't be there for *generic* arm ostree updates as it's a platform specific u-boot package. Signed-off-by:
Sjoerd Simons <sjoerd.simons@collabora.co.uk> Reviewed-by:
Denis Pynkin <denis.pynkin@collabora.com> Differential Revision: https://phabricator.apertis.org/D7859
-
Denis Pynkin authored
Kernel is updated to use standardized version for all platforms. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com> Reviewed-by:
Frédéric Dalleau <frederic.dalleau@collabora.co.uk> Differential Revision: https://phabricator.apertis.org/D7837
-
- Apr 05, 2018
-
-
As new version of mesa package that we updated in apertis that already dropped libegl1-mesa-drivers transitional package. So that we shouldn't keep install libegl1-mesa-drivers from our images. This commit is to drop libegl1-mesa-drivers from ospack, uefi and sdk images. Signed-off-by:
Andrew Lee (李健秋) <andrew.lee@collabora.co.uk> Reviewed-by:
Andrew Shadura <andrew.shadura@collabora.co.uk> Differential Revision: https://phabricator.apertis.org/D7779
-
- Apr 04, 2018
-
-
Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com> Signed-off-by:
Andrew Shadura <andrew.shadura@collabora.co.uk>
-
- Mar 15, 2018
-
-
Andrej Shadura authored
Debos requires mountpoint options to be a list; they are ignored silently if it isn't. Apertis: https://phabricator.apertis.org/T4664 Signed-off-by:
Andrew Shadura <andrew.shadura@collabora.co.uk> Reviewed-by:
Denis Pynkin <denis.pynkin@collabora.com> Differential Revision: https://phabricator.apertis.org/D7702
-
- Dec 20, 2017
-
-
Signed-off-by:
Andrew Shadura <andrew.shadura@collabora.co.uk> Reviewed-by:
Héctor Orón Martínez <hector.oron@collabora.co.uk> Reviewed-by:
Emanuele Aina <emanuele.aina@collabora.co.uk> Differential Revision: https://phabricator.apertis.org/D7395
-
- Dec 12, 2017
-
-
Luis Araujo authored
This commit removes printf and use concatenation to get the .img suffix in the images names. Signed-off-by:
Luis Araujo <luis.araujo@collabora.co.uk> Reviewed-by:
Sjoerd Simons <sjoerd.simons@collabora.co.uk> Differential Revision: https://phabricator.apertis.org/D7346
-
- Dec 08, 2017
-
-
Luis Araujo authored
This commit removes adding a global suffix from the Jenkinsfile for the images and instead add the suffix from the uboot and uefi boards template (like the sdk template already does). Signed-off-by:
Luis Araujo <luis.araujo@collabora.co.uk> Reviewed-by:
Denis Pynkin <denis.pynkin@collabora.co.uk> Differential Revision: https://phabricator.apertis.org/D7341
-
- Nov 21, 2017
-
-
Sjoerd Simons authored
There is nothing specific in this image recipe to amd64, all it assumes is that the board has a uefi first stage bootloader. This exists not just for amd64, but also for for example 64 bit arm and 32 bit arm. Signed-off-by:
Sjoerd Simons <sjoerd.simons@collabora.co.uk> Reviewed-by:
Héctor Orón Martínez <hector.oron@collabora.co.uk> Differential Revision: https://phabricator.apertis.org/D7246
-
- Nov 10, 2017
-
-
Denis Pynkin authored
Initial version of recipes allows to create Apertis images for amd64 architecture. Development and SDK images are not fully functional yet. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com> Reviewed-by:
Frédéric Dalleau <frederic.dalleau@collabora.co.uk> Reviewed-by:
Emanuele Aina <emanuele.aina@collabora.co.uk> Differential Revision: https://phabricator.apertis.org/D7204
-