diff options
author | Stefan Agner <stefan.agner@toradex.com> | 2020-04-28 18:54:39 +0000 |
---|---|---|
committer | Stefan Agner <stefan.agner@toradex.com> | 2020-05-07 21:06:55 +0000 |
commit | 48c0442f926940346e2d4fa693c49cb7419917bf (patch) | |
tree | cdd2b2c827647b5e2f304e4399305d395d3378d3 /classes/target_version_example.bbclass | |
parent | fcc397f16efde0c053c8a96e7500147ab84cb8d3 (diff) | |
download | meta-updater-48c0442f926940346e2d4fa693c49cb7419917bf.tar.gz |
image_types_ota: use named reference
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 <stefan.agner@toradex.com>
Diffstat (limited to 'classes/target_version_example.bbclass')
0 files changed, 0 insertions, 0 deletions