From 47943c194cc5ee9b09d77f5c3a6399febce25811 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 2 Sep 2026 14:55:45 +0000 Subject: [PATCH 1/2] chore(deps): update dependency kernel-rt-7.2 to v7.2.3 --- configs/mister_rt.fragment | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configs/mister_rt.fragment b/configs/mister_rt.fragment index 605a89e..371fcdb 100644 --- a/configs/mister_rt.fragment +++ b/configs/mister_rt.fragment @@ -64,7 +64,7 @@ # exemption, so the tarball MUST have a sha256 line there or the build fails # closed at download. Bump the version here -> update that line in the same # commit (its header says where the value must come from). -BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="7.2.2" +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="7.2.3" # --- Beta patch set ----------------------------------------------------------- # linux-patches-beta/ is a series-file-driven SUBSET of linux-patches/: symlinks From 16e044f23ecd72097e0cfe82f036557bebd9e87a Mon Sep 17 00:00:00 2001 From: "renovate-hash-sync[bot]" Date: Wed, 2 Sep 2026 14:56:15 +0000 Subject: [PATCH 2/2] renovate-hash-sync: refresh companion hash(es) for this PR Recomputed from a freshly-fetched artifact: - driver/firmware/libchdr package pins: sha256sum of the github archive tarball at the new pinned owner/repo/ref (same "locally computed" practice this tree's own .hash file headers already document) - kernel pins (stable 6.18.y and the RT/beta 7.2 line): kernel.org's signed sha256sums.asc for each pin's own vN.x series. An -rc is never refreshed here -- no signed manifest exists for one - lzma-sdk pin: sha256sum of the ip7z/7zip release ASSET for the new version (upstream publishes no checksums at all -- see package/lzma-sdk/lzma-sdk.hash's header) - sdcard payload pins (update_all.sh, wifi.sh): sha256 + size of the raw file at the new pinned commit, rewritten in place in scripts/fetch-sdcard-payload.sh - Buildroot pin (BUILDROOT_SHA256, root Makefile): transcribed from buildroot.org's GPG-signed release manifest (buildroot-.tar.gz.sign) -- the same signed file `make buildroot-showsig` prints, never a locally-computed sha256sum of the tarball (that remains forbidden; see the Makefile's own header comment) - azcopy pin: REBUILT, not fetched. Buildroot's own support/download/go-post-process re-ran `go mod vendor` over the newly pinned tag with the Go version the pinned Buildroot tree pins, and the resulting azcopy--go2.tar.gz was hashed -- the only way this value can be derived, since no URL serves that file (see package/azcopy/azcopy.hash's header). LICENSE and NOTICE.txt were re-hashed from the same tarball --- board/mister/de10nano/patches/linux/linux.hash | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/board/mister/de10nano/patches/linux/linux.hash b/board/mister/de10nano/patches/linux/linux.hash index 7dee7ba..52c6d85 100644 --- a/board/mister/de10nano/patches/linux/linux.hash +++ b/board/mister/de10nano/patches/linux/linux.hash @@ -90,4 +90,4 @@ sha256 5ebdadb10a4b5708fc6b1c457764a110bc49f8150cc3502c59b921ead8c6fc8c linux- # also the one case scripts/hash-sync-kernel.sh refuses to automate -- it # declines any value containing "-rc" and leaves this line alone, so the build # fails closed rather than blessing a snapshot nobody looked at. -sha256 7d0e7ce14f98c43efe880cffbf354a59be45928fdf7170d7333c374ae91c0d83 linux-7.2.2.tar.xz +sha256 8ba259e8e7b13ec6ef0941c8a39ad90b24bd4a4d6c0010ba6bafb794550ecd03 linux-7.2.3.tar.xz