linux/meta-updater.git/conf, branch feat/OTA-2150/system_monitoringMirror of github.com/advancedtelematic/meta-updaterhttps://git.enea.com/cgit/linux/meta-updater.git/atom?h=feat%2FOTA-2150%2Fsystem_monitoring2019-12-04T10:46:30+00:00Force a simple reproducible build mechanism2019-12-04T10:46:30+00:00Laurent Bonnanslaurent.bonnans@here.com2019-12-04T10:39:58+00:00urn:sha1:af1694c7044aee54761750080819d5c5d6ce09e4
In 25a17f0346ab05b3212bb280e4a8b622bcf99bce, poky sets
reproducible_build by defaults. However, it is quite complex as it tries
to compute a plausible timestamp from source files, in a reproducible
ways.
Setting the timestamps to 0, just like ostree, is probably safer in our
case, so let's switch to our old behavior.
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
OTA-3988: Split the local.conf to a base and a distro specific part2019-11-06T12:35:34+00:00Mykhaylo Sulext-mykhaylo.sul@here.com2019-11-06T08:44:03+00:00urn:sha1:c74c4eb5399ed7a195e00172774a283582da6e44
Signed-off-by: Mykhaylo Sul <ext-mykhaylo.sul@here.com>
OTA-3988: make the DISTRO value in poky-sota-systemd.conf aligned to the systemd case2019-11-05T16:35:43+00:00Mykhaylo Sulext-mykhaylo.sul@here.com2019-11-05T16:35:43+00:00urn:sha1:3f904325ad5d307f308e020e9bc4d24a8afdf7af
Signed-off-by: Mykhaylo Sul <ext-mykhaylo.sul@here.com>
OTA-3988: force an ostree boot indication only in case of non-systemd distro2019-11-05T09:09:25+00:00Mykhaylo Sulext-mykhaylo.sul@here.com2019-11-05T08:17:53+00:00urn:sha1:40153ba5d77a83e78a9b844a8117b44be8b55df0
Signed-off-by: Mykhaylo Sul <ext-mykhaylo.sul@here.com>
OTA-3988: Non-systemd/poky-sota local.conf2019-11-01T10:02:30+00:00Mykhaylo Sulext-mykhaylo.sul@here.com2019-11-01T10:02:30+00:00urn:sha1:6680bfb70ce2285ef5243e489073fb26bc63f0e7
Signed-off-by: Mykhaylo Sul <ext-mykhaylo.sul@here.com>
aktualizr-device-prov-creds: remove it.2019-10-18T11:34:13+00:00Patrick Vacekpatrickvacek@gmail.com2019-10-17T15:01:18+00:00urn:sha1:3f70b2d2f4a3a2fb50be4b8c395d9d09b0853f1a
Originally I was just trying to remove the reference to DEPLOY_DIR_IMAGE
because it depends on MACHINE, but then I realized that this recipe is
just plain not worth keeping. It isn't viable for anything except the
most limited testing, since it bakes device-specific credentials into an
image, but we weren't even using it for testing.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
layer.conf: Update LAYERDEPENDS_sota.2019-10-17T15:03:38+00:00Patrick Vacekpatrickvacek@gmail.com2019-10-14T10:30:49+00:00urn:sha1:d1118a121810c5c76e33a63909d43b4e25439250
It was missing a few dependencies.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
aktualizr: use SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS for config recipes.2019-10-17T15:03:38+00:00Patrick Vacekpatrickvacek@gmail.com2019-10-14T10:06:23+00:00urn:sha1:837b2fc0f2ccf6d334ebf026a44f3ea0f83323a7
This is a bit of a compromise. These recipes are allarch, since they do
not depend on an architecture, but they depend on aktualizr, which is
definitely not allarch. Therefore, we must tell bitbake not to treat the
aktualizr architecture as a dependency of these recipes.
However, this means that if one of the config files changes in the
aktualizr repo, we need to bump the version of the recipe that uses it
to make sure bitbake picks up that change.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
Raspberrypi4 initial support2019-09-17T13:55:33+00:00Laurent Bonnanslaurent.bonnans@here.com2019-09-05T14:59:18+00:00urn:sha1:5296877819e156e5006946cc6f626908057172d1
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
layer.conf: add zeus to compatible release series2019-09-04T22:52:43+00:00Ricardo Salvetiricardo@foundries.io2019-09-04T22:52:16+00:00urn:sha1:ac7df811cb7589dd6d199ca3d7cde6d606e46f25
Zeus is the next OE release, scheduled to be released in October/2019.
Signed-off-by: Ricardo Salveti <ricardo@foundries.io>