linux/meta-updater.git, branch testing-do-not-merge

aktualizr: Bump to latest.

2020-06-23T13:28:21+00:00

Signed-off-by: Patrick Vacek

Merge pull request #736 from advancedtelematic/feat/secondary-aktualizr-info

2020-06-23T12:11:18+00:00

Put aktualizr-info in a separate package and use it in Secondaries.

2020-06-23T11:00:17+00:00

We did the work a while ago to make aktualizr-info work for Secondaries, but until now we weren't putting the tool into the secondary-image we use for testing. Now it's there. Actually, it's in every image that inherits from sota.bbclass, which is probably a good thing. Signed-off-by: Patrick Vacek

Merge pull request #681 from liuming50/introduce-ostree-kernel-initramfs

2020-06-22T07:39:49+00:00

Introduce ostree kernel initramfs

Merge pull request #722 from liuming50/fix-network-configuration-naming

2020-06-22T07:29:26+00:00

meta: change virtual/network-configuration to network-configuration

meta: introduce ostree-kernel-initramfs recipe

2020-06-18T17:48:12+00:00

We package kernel image, devicetrees, initramfs and install them to /usr/lib/modules/${KERNEL_VERSION}, which is the preferred location according to ostree's new implementation, this could simplify the deployment. Reference: https://github.com/ostreedev/ostree/commit/3ab0d5e6644885440bac6abd17b6d2637df5435f To let initramfs-ostree-image be able to be depended by ostree-kernel-initramfs, it must inherit nopackages to avoid a annoying QA warning like the follows: | WARNING: initramfs-ostree-image-0.0.1-r0 do_package: Manifest ...initramfs-ostree-image.packagedata | not found in colibri_imx6 armv7ahf-neon-imx armv7at2hf-neon-imx armv7at2hf-neon armv7ahf-neon armv7at2hf-vfp | armv7ahf-vfp armv6thf-vfp armv6hf-vfp armv5tehf-vfp armv5ehf-vfp armv5thf-vfp armv5hf-vfp allarch | x86_64_x86_64-nativesdk (variant '')? Also we need define OSTREE_KERNEL, OSTREE_DEPLOY_DEVICETREE and OSTREE_DEVICETREE in sota.bbclass so they could be accessed in other recipes as well as in image recipes. Signed-off-by: Stefan Agner Signed-off-by: Ming Liu

Merge pull request #734 from agners/use-boot-complete

2020-06-18T13:11:12+00:00

aktualizr: make use of boot-complete.target

Merge pull request #735 from advancedtelematic/test/OTA-4838/mem-binary-update

2020-06-18T11:17:59+00:00

Add recipe to build images with binary primaries

2020-06-18T09:35:53+00:00

Signed-off-by: Laurent Bonnans

aktualizr: make use of boot-complete.target

2020-06-15T09:42:19+00:00

From the systemd.special(7) man page section boot-complete.target: This target is intended as generic synchronization point for services that shall determine or act on whether the boot process completed successfully. Let's make use of the target. Since aktualizr by default marks a boot as successful, we consider aktualizr.service a service which needs to be executed on successful boot (hence after the boot-complete.target). This allows to declare a service as crucial by simply ordering it before the boot-complete.target. The systemd example service systemd-boot-check-no-failures.service can serve as an example. This change does not add any service dependency by default as boot-complete.target by default does not has any extra dependencies. Note that rebooting in the failure case is not handled by this mechanism. This can be added by using FailureAction. Boot assessement infrastructure got introduced with systemd 240. See also: https://systemd.io/AUTOMATIC_BOOT_ASSESSMENT/ Signed-off-by: Stefan Agner