linux/meta-updater.git/recipes-sota/aktualizr, branch master

Convert to new override syntax

2021-07-30T08:29:35+00:00

This is the result of automated script (0.9.0) conversion: oe-core/scripts/contrib/convert-overrides.py . converting the metadata to use ":" as the override character instead of "_". Signed-off-by: Martin Jansa

aktualizr: drop unnecessary do_configure_prepend

2021-04-30T11:51:24+00:00

* fails with latest oe-core/master with: https://git.openembedded.org/openembedded-core/commit/meta/classes/cmake.bbclass?id=0fb6280432a36985590d9a714a5f11164aaebb51 because this prepend does "cd ${S}" and doesn't go back to ${B} and cmake_do_configure function doesn't cd to ${B} anymore, resulting in: | CMake Error at CMakeLists.txt:42 (message): | Aktualizr does not support building in the source tree. Please remove | CMakeCache.txt and the CMakeFiles/ directory, then create a subdirectory to | build in: mkdir build; cd build; cmake .. * drop this whole do_configure_prepend as git-native works fine: aktualizr-native/1.0+gitAUTOINC+1255aa24fe-7/git$ grep Setting ../temp/log.do_configure -- Setting version to 2020.10-0-g1255aa24f aktualizr/1.0+gitAUTOINC+1255aa24fe-7/temp$ grep Setting ../temp/log.do_configure -- Setting version to 2020.10-0-g1255aa24f aktualizr/1.0+gitAUTOINC+1255aa24fe-7/build$ which git /OE/build/oe-core/tmp-musl/hosttools/git aktualizr/1.0+gitAUTOINC+1255aa24fe-7/build$ grep GIT CMakeCache.txt GITCOMMAND:FILEPATH=/OE/build/oe-core/tmp-musl/hosttools/git GIT_EXECUTABLE:FILEPATH=/OE/build/oe-core/tmp-musl/hosttools/git //ADVANCED property for variable: GITCOMMAND GITCOMMAND-ADVANCED:INTERNAL=1 //ADVANCED property for variable: GIT_EXECUTABLE GIT_EXECUTABLE-ADVANCED:INTERNAL=1 Signed-off-by: Martin Jansa

aktualizr: Don't put unused configs in the image.

2020-11-03T15:51:54+00:00

Because every aktualizr package was depending on aktualizr-configs, all of the default configs were getting installed to /usr/lib/sota, despite that by default none of them were ever used on the device. That dependency has been removed. The provisioning recipes still install the recipes they need to the default location that aktualizr actually uses (/usr/lib/sota/conf.d). If you want to use anything else, a specific recipe should be created to do so. This change rendered the aktualizr-host-tools package useless, so it has been removed. Signed-off-by: Patrick Vacek

aktualizr: Upgrade to 2020.10 release

2020-11-03T15:51:54+00:00

Signed-off-by: Anatoliy Odukha

aktualizr: Upgrade to 2020.9 release.

2020-08-26T08:25:33+00:00

Signed-off-by: Patrick Vacek

aktualizr: Bump to latest and install headers in dev package.

2020-08-06T06:30:42+00:00

Signed-off-by: Patrick Vacek

aktualizr: Bump to 2020.8 release.

2020-07-09T15:02:56+00:00

Signed-off-by: Patrick Vacek

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

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

Bump aktualizr to 2020.7 revision

2020-05-29T09:30:53+00:00

And garage-sign to 0.7.1-4 Signed-off-by: Laurent Bonnans