From eaa0b0741b149bf96036d83b4510c2432395c6aa Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Thu, 20 Aug 2026 16:22:42 -0400 Subject: [PATCH] Pin forgefirm-app and forgectrl to the same tree Same repository as the python3-gfhardware pin in meta-glowforge-bsp, moved with it. forgectrl moves for the download guards it exposes to the panel. --- meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc | 2 +- .../recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc b/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc index b43204c..7f7b264 100644 --- a/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc +++ b/meta-forgefirm/recipes-forgefirm/forgectrl/forgectrl-pin.inc @@ -2,5 +2,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 = "cb860dc607fa9f37f90548feb05f534da77a956b" +SRCREV = "01fb0244657a506c24a55339af6d7f3e86838464" PV = "0.1.0" diff --git a/meta-forgefirm/recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc b/meta-forgefirm/recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc index 32c069f..f4065d5 100644 --- a/meta-forgefirm/recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc +++ b/meta-forgefirm/recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc @@ -4,9 +4,9 @@ # because the component entry already identifies the pinned source # (forgefirm-image-manifest.bbclass). The python3-gfhardware recipe in # meta-glowforge-bsp pins the same repository; move both together. -SRCREV = "63d6d454d4289c5f2df4347d42d1dcf7227fa7a2" +SRCREV = "f188e4098611663f0649b502f9f31ccc7fd4a4f7" # Bump PV with every SRCREV move: the hash-derived package version is not # monotonic on its own and buildhistory QA fails the build when it sorts # backwards. -PV = "0.1.11+git" +PV = "0.1.12+git"