linux/meta-updater.git, branch feat/collectd

Adding collectd coniguration for aktualizr

2020-05-13T12:12:06+00:00

Signed-off-by: Laurent Bonnans

Merge pull request #716 from agners/master-ostree-fix-deployment-ref

2020-05-12T15:16:39+00:00

Use checksum as deployment source and refspec in the deployment

Merge pull request #723 from liuming50/drop-qemuboot-from-initramfs-ostree-image

2020-05-12T11:51:04+00:00

initramfs-ostree-image: drop qemuboot from IMAGE_CLASSES

Merge pull request #724 from liuming50/fix-an-incomplete-sanity-checking

2020-05-12T10:15:30+00:00

sota_sanity.bbclass: introduce sota_check_boolean_variable

2020-05-11T17:53:55+00:00

The current sanity check are too strict for some boolean variables, introduce sota_check_boolean_variable to allow a boolean value to be set like yes/y/true/t/1 or no/n/false/f/0. Also change to use oe.types.boolean to check their values. Signed-off-by: Ming Liu

initramfs-ostree-image: drop qemuboot from IMAGE_CLASSES

2020-05-11T11:54:48+00:00

To avoid generating a qemuboot.conf for qemu machines, it's useless for a initramfs image. Signed-off-by: Ming Liu

image_types_ota: use named reference

2020-05-07T21:06:55+00:00

Use named reference when deploying the device tree. This makes sure that this reference will end up in the deployments .origin file, which will be visible by the user in ostree admin status. This reference will also be used when running ostree admin upgrade. This is not really required when using aktualizr, but can be useful during test/debugging when using pure OSTree updates. Make sure to make ${OSTREE_REPO} accessible via http and add a remote on the device called ${OSTREE_OSNAME} pointing to the http exposed archive OSTree. With that ostree admin upgrade should work. Note: We could use the name reference in ostree pull-local already, but this is potentially racy if multiple builds are committing to the same branch. Use the OSTree commit hash to get the actual commit and recreate a local reference to this commit. This makes absolutely sure that we use the same OSTree commit this bitbake execution committed during the do_image_ostreecommit task. Signed-off-by: Stefan Agner

image_types_ostree/ota: use hash from ostree commit

2020-05-07T21:06:55+00:00

Relying on a OSTree branch reference has been problematic in the past and addressed by adding more attributes to it in commit 202a8c70ba8c ("image_types_ostree: Add a unique ref to fix simultaneous bitbaking."). However, depening on what kind of OpenEmbedded builds are running in parallel, even more attributes would need to be taken into account. Instead of relying on a reference, store the exact ostree commit hash in a manifest file and reuse it in the do_image_ota deploy task. This guarantees that the correct reference gets picked even when two builds with the exact same machine/image name run in parallel. Note: This gets rid of the second branch name again. If the branch name with image name is preferred, the variable OSTREE_BRANCHNAME can be used: OSTREE_BRANCHNAME = "${SOTA_HARDWARE_ID}-${IMAGE_BASENAME}" Signed-off-by: Stefan Agner

Merge pull request #713 from agners/master-ostree-improvements

2020-05-05T12:11:26+00:00

OSTree task improvements

Merge pull request #717 from advancedtelematic/feat/2020.6

2020-04-30T11:34:40+00:00

aktualizr: Update to 2020.6 release and garage-sign 0.7.1.