mirror of
https://github.com/openglow-org/forgefirm.git
synced 2026-09-28 09:11:11 -07:00
ScottW514
f4b70a0826
The full acceptance campaign on dev image 20260821181036, the first built on the <recipe>-pin.inc layout, satisfied 42 of 42 and its export authorizes a release, so the status header, the acceptance section and item 12 describe that rather than a campaign still owed; the catalog count is 42, not 35. CAMPAIGN-LOG records the completion. Item 7 stops listing the cloud work the campaign closed (the oversize live print, the progress bar watched from the app, packaged-path cloud boot, the lid flash), records the operator's declines (SPKI pinning, emulator parity, the ten-event pause machine) and the reasoned memory guards, and item 19 no longer lists MCsn and PDfm as unchecked: the client refuses both, so seventeen mandatory tags are dropped, not nineteen. forgefirm-app pin moves to b82d379 (python3-gfhardware): CLOUD.md and three present-tense comments, no behavior change. No catalog consequence beyond the pin bump itself, which the manifest scopes to the component.
13 lines
660 B
PHP
13 lines
660 B
PHP
# forgefirm-app pin (python3-gfhardware repository, forgefirm-app/ tree).
|
|
# Bump deliberately (AUTOREV is not reproducible); keep 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). The python3-gfhardware recipe in
|
|
# meta-glowforge-bsp pins the same repository; move both together.
|
|
SRCREV = "b82d37984b16ee426f24eaf980346b3692e9af5d"
|
|
|
|
# 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.13+git"
|