summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJeremias Cordoba <js.cordoba8321@gmail.com>2019-10-15 16:21:42 -0700
committerJeremias Cordoba <js.cordoba8321@gmail.com>2019-10-15 16:21:42 -0700
commit8e53d0cbed00e38deb83cea396a899ef74201f8f (patch)
tree50e8b1b9700ada8b3c2e176019a7b6fe3193978a
parenta1f2ccf986e844e130ecc6ae61d2b6fc3632e2f8 (diff)
downloadmeta-updater-8e53d0cbed00e38deb83cea396a899ef74201f8f.tar.gz
image_types_ostree: Fix OSTree ref-bindingsfix-ref-binding
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>
-rw-r--r--classes/image_types_ostree.bbclass3
1 files changed, 2 insertions, 1 deletions
diff --git a/classes/image_types_ostree.bbclass b/classes/image_types_ostree.bbclass
index 795e01b..7ffe99d 100644
--- a/classes/image_types_ostree.bbclass
+++ b/classes/image_types_ostree.bbclass
@@ -168,7 +168,8 @@ IMAGE_CMD_ostreecommit () {
168 --skip-if-unchanged \ 168 --skip-if-unchanged \
169 --branch=${OSTREE_BRANCHNAME} \ 169 --branch=${OSTREE_BRANCHNAME} \
170 --subject="${OSTREE_COMMIT_SUBJECT}" \ 170 --subject="${OSTREE_COMMIT_SUBJECT}" \
171 --body="${OSTREE_COMMIT_BODY}" 171 --body="${OSTREE_COMMIT_BODY}" \
172 --bind-ref="${OSTREE_BRANCHNAME}-${IMAGE_BASENAME}"
172 173
173 if [ "${OSTREE_UPDATE_SUMMARY}" = "1" ]; then 174 if [ "${OSTREE_UPDATE_SUMMARY}" = "1" ]; then
174 ostree --repo=${OSTREE_REPO} summary -u 175 ostree --repo=${OSTREE_REPO} summary -u