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.
This commit is contained in:
ScottW514
2026-08-20 16:22:42 -04:00
parent 54d238d67d
commit eaa0b0741b
2 changed files with 3 additions and 3 deletions
@@ -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"
@@ -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"