From 87155be4339b50f3c39c8c8f27db669f1a4586e5 Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Thu, 15 Oct 2026 08:13:41 -0400 Subject: [PATCH] Pin forgectrl 0.1.32 on the pushed head - forgectrl c9e3347 -> 22a2cfc (0.1.31 -> 0.1.32): fflog_e2e runs its private rsyslogd from a copy of the binary, out of reach of Ubuntu's AppArmor profile for /usr/sbin/rsyslogd. The diff is tests/fflog_e2e.sh alone; nothing the image installs changes. At c9e3347 the CI run stopped at fflog_e2e, so host_routes.sh and host_setup.sh, later in the same job, never ran there. The rows the next catalog commit adds name those two scripts and fflog_e2e.sh, and the coverage lint reads build.yml at this pin, so the pin is the revision whose run executed them. Proof: forgectrl's CI run on 22a2cfc (38728407038) is green; fflog_e2e, host_routes, host_setup and jobpost_test passed in it. --- 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 e98a47e..f65f5ed 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 = "c9e3347bdcc6535056e5de5e1d4bd38e93de9494" -PV = "0.1.31" +SRCREV = "22a2cfc04242ddc50ed0a54e967a59634f3f4d6d" +PV = "0.1.32"