From c3468e64fb76f5cbd94f8bb574bc258a73f057a0 Mon Sep 17 00:00:00 2001 From: "Michael C. Ferguson" Date: Sat, 5 Sep 2026 23:12:25 -0500 Subject: [PATCH] golden: refresh the de25nano hash for image-common (semantic merge of #141 and #150) master went red at lint-config after both PRs landed. Neither is wrong and git reported no conflict -- they collided semantically, in the resolved config rather than in any file's text. #141 added `image-common` to DE25NANO_FRAGMENTS, so the de25nano stack resolves from three fragments instead of two (55 -> 86 fragment symbols). #150 recorded the 2026.08 golden hashes against the two-fragment composition, which was correct when it was written. Merged, the recorded de25nano hash describes a stack that no longer exists: expected 81e7f4e6, actual 68cc9ed6. Only de25nano moved. de10nano also gained image-common in #141, but its hash is unchanged (fccaabea) because that half of the refactor only relocated symbols that were already in de10nano-image -- which is exactly the evidence that the DE10 image this repo actually builds and ships is byte-identical to the one #150 validated at 176/176. de10nano-kernel and rt do not take image-common at all and are untouched. REVIEWED, NOT JUST REGENERATED -- this bump has already burned that lesson once (#150's first golden regeneration baked in a uClibc regression). Resolved the de25nano config with and without image-common and diffed: 33 lines, ALL additions, ZERO removals, all of them BR2_PACKAGE_LINUX_FIRMWARE* -- the WiFi/BT firmware set #141 deliberately hoisted so both images select it once instead of mirroring it per board. Nothing else moved: BR2_TOOLCHAIN_USES_GLIBC, BR2_KERNEL_HEADERS_7_1 / 7.1.13, gcc 15.3.0 all intact and BR2_LEGACY clear, so #150's headers fix survived the merge. The drift is #141's intent, and the golden line is what needed to catch up. Note for DE25 specifically: it now pulls linux-firmware, which it did not before. That is #141's design decision, not a side effect of this fix. `check-config-fragments.sh` now passes on all 4 stacks; the other three lint steps in that job were already green. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01PFQovqPVshbtdzJnZyr5bc --- configs/fragments/golden.sha256 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configs/fragments/golden.sha256 b/configs/fragments/golden.sha256 index 8cba93e..4b77f16 100644 --- a/configs/fragments/golden.sha256 +++ b/configs/fragments/golden.sha256 @@ -6,7 +6,7 @@ # 2026.08 de10nano fccaabea951a6d8b8f65f16bf85d199046eae9bacf6ea5102f5a1842317870b6 2026.08 de10nano-kernel b69db3e12782bfede48587acbb9549a0f2ef794acb6b8a41d5c95bc112a91104 -2026.08 de25nano 81e7f4e613aafa3114768db14eadbc66c778f310e10dd1d163acfbbe1e7289b6 +2026.08 de25nano 68cc9ed6191e9539098c8307a6f470830c70a8f640ef37e05379c1b96e6b6e88 2026.08 rt 103e68329df556920a06b736bcbafcad3913ce3ce49ef75f448df2797465ad95 2026.05.2 de10nano 251ae321011945e690a32f2fbb704b619681fd26d06acf578f7691e76286f992 2026.05.2 de10nano-kernel 5b372abe43c46c4eb5f3c88d51e48ff2eb6fa713b3c02f0f337c39d0f111dc69