From 29b00cc056d31d5be06aa9bbdd555d2e822b4b76 Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Sat, 19 Sep 2026 16:22:43 -0400 Subject: [PATCH] Pin forgectrl 0.1.27 (the export carries the installer's log) forgectrl 7a9de005ede5 -> 0dae758cb93e (PV 0.1.26 -> 0.1.27) forgectrl 0dae758 stages logs/install/ into the log export, which is what logs.tree-tail-export now requires of the bundle. The PV moves with the SRCREV so the hash-derived package version stays monotonic. Proven: bitbake -c fetch forgectrl resolves the pin (forgectrl-1_0.1.27-r0 do_fetch succeeded). --- meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc b/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc index c5905eb..fbd6346 100644 --- a/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc +++ b/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc @@ -4,5 +4,5 @@ # only SRCREV and PV here - the image manifest leaves *-pin.inc out of the # layer content hash because the component entry already identifies the # pinned source (forgefirm-image-manifest.bbclass). -SRCREV = "7a9de005ede5a98290b81e653934a3dcda795719" -PV = "0.1.26" +SRCREV = "0dae758cb93e1461034aaa58f4b9fc22edc68367" +PV = "0.1.27"