os-release: only run bbappend on do_compile
Chasing an intermittent os-release build failure via
openbmc/openbmc#3720. Not clear if this fix will resolve
that issue but there does not appear to be any reason to
run the logic in the bbappend outside of the do_compile
step since that is the only place the OS_RELEASE_FIELDS
are utilized by the base recipe.
(From meta-phosphor rev: f2b07859cc9586f96b072678d1f5f4586e77850b)
Change-Id: I5f14da2babc852f3d39f2ca6bae4bf993d5e22da
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
diff --git a/meta-phosphor/recipes-core/os-release/os-release.bbappend b/meta-phosphor/recipes-core/os-release/os-release.bbappend
index c010146..1c98781 100644
--- a/meta-phosphor/recipes-core/os-release/os-release.bbappend
+++ b/meta-phosphor/recipes-core/os-release/os-release.bbappend
@@ -13,7 +13,7 @@
except:
pass
-python() {
+python do_compile_prepend() {
version_id = run_git(d, 'describe --dirty --long')
if version_id:
d.setVar('VERSION_ID', version_id)