linux/meta-updater.git, branch feat/thud/2019.9-backportMirror of github.com/advancedtelematic/meta-updaterhttps://git.enea.com/cgit/linux/meta-updater.git/atom?h=feat%2Fthud%2F2019.9-backport2019-10-29T16:07:14+00:00Fix aktualizr-ptest breakage2019-10-29T16:07:14+00:00Laurent Bonnanslaurent.bonnans@here.com2019-10-28T13:44:07+00:00urn:sha1:c1766d6b3e4d7aa514dca098f49aaee8e33e08de
The compile step was removed by mistake in ec1ac0617b120813d6450dffe1aa8d4868e37332!
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
networkd-dhcp-conf: Remove allarch.2019-10-29T16:07:14+00:00Patrick Vacekpatrickvacek@gmail.com2019-10-28T08:57:11+00:00urn:sha1:2207fe9f85cbf998948a5645178cd673ac5647c2
We were setting PACKAGE_ARCH to MACHINE_ARCH anyway, so this wasn't
helping anything.
Suggested-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
aktualizr: remove systemd from PACKAGECONFIG.2019-10-29T16:07:14+00:00Patrick Vacekpatrickvacek@gmail.com2019-10-22T14:22:10+00:00urn:sha1:dbc841d33a9ffc10a5a7ddc2baacb41aa9282129
The systemd functionality in aktualizr is not currently used for
anything, so there's no reason to use it.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
Default bblayers.conf for rpi3-64 also requires meta-python.2019-10-29T16:07:14+00:00Patrick Vacekpatrickvacek@gmail.com2019-10-21T11:25:07+00:00urn:sha1:f22f8651f741c76d087a431f5aa334515b12a34b
In warrior and newer branches, meta-python is required by everything,
but for thud and earlier, it's only necessary for RPi. That said, I'm
not sure why rpi2 has never used it.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
aktualizr: Bump to 2019.9 release and latest garage-sign.2019-10-29T16:07:14+00:00Patrick Vacekpatrickvacek@gmail.com2019-10-21T07:40:06+00:00urn:sha1:aa8d68a6defb4676ade11ad5ebc610557d8d4cce
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
image_types_ostree: Fix OSTree ref-bindings2019-10-29T16:07:14+00:00Jeremias Cordobajs.cordoba8321@gmail.com2019-10-15T23:21:42+00:00urn:sha1:b1ee116da9eb279991ce61d8114fa0354b45b35d
The command "ostree refs --create" creates a new ref that points to a pre-existing commit hash.
This does not add this new ref to the ref-bindings metadata in OSTree.
The missing metadata leads to OSTree verifcation failures when working with the new ref.
Fix this by adding the "--bind-ref" option to "ostree commit" which adds the needed
ref-binding metadata.
Signed-off-by: Jeremias Cordoba <js.cordoba8321@gmail.com>
aktualizr-device-prov-creds: remove it.2019-10-21T11:22:04+00:00Patrick Vacekpatrickvacek@gmail.com2019-10-17T15:01:18+00:00urn:sha1:0817c87667e67aa40a2e07ad8b15f17c74927e2b
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>
Specify more configs as MACHINE_ARCH.2019-10-21T11:22:04+00:00Patrick Vacekpatrickvacek@gmail.com2019-10-16T14:54:55+00:00urn:sha1:4bcb164063a1a12f1cc12165934bcaeaa81732a7
If they depend on MACHINE, that's what we gotta do. Still haven't sorted
out aktualizr-device-prov-creds, though.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
Split aktualizr hwid config to another recipe2019-10-21T11:22:04+00:00Laurent Bonnanslaurent.bonnans@here.com2019-10-15T16:58:24+00:00urn:sha1:3b2b6e485c4ade61296322f4e1efae09c04e396a
So that we can fix the ${MACHINE} dependency issues
Signed-off-by: Laurent Bonnans <laurent.bonnans@here.com>
layer.conf: Update LAYERDEPENDS_sota.2019-10-21T11:22:04+00:00Patrick Vacekpatrickvacek@gmail.com2019-10-14T10:30:49+00:00urn:sha1:9c700dc94dcf1966dca94e1b0c11f7c20384f2b7
It was missing a few dependencies.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>