From 0203887dc9d799d767a74f5a7d5606e79465d6c4 Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Thu, 20 Aug 2026 07:48:31 -0400 Subject: [PATCH] Pin forgefirm-app to the streamed-pause client Same repository as the python3-gfhardware pin in meta-glowforge-bsp, moved with it: the cloud client now sizes a pause to the history the ring kept. --- .../recipes-forgefirm/forgefirm-app/forgefirm-app-pin.inc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) 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 716ed0a..32c069f 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 = "a3907f6b24134aeb3ad3812eed55d05834e8320b" +SRCREV = "63d6d454d4289c5f2df4347d42d1dcf7227fa7a2" # 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.10+git" +PV = "0.1.11+git"