From 4d3cdf96d7c176465af2f4becd9d1beb1c5f9c53 Mon Sep 17 00:00:00 2001 From: "renovate[bot]" <29139614+renovate[bot]@users.noreply.github.com> Date: Wed, 2 Sep 2026 14:55:39 +0000 Subject: [PATCH 1/2] chore(deps): update dependency kernel-longterm-6.18 to v6.18.49 --- configs/mister_de10nano_defconfig | 4 ++-- configs/mister_kernel_defconfig | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/configs/mister_de10nano_defconfig b/configs/mister_de10nano_defconfig index 14e2e35..073acc5 100644 --- a/configs/mister_de10nano_defconfig +++ b/configs/mister_de10nano_defconfig @@ -38,7 +38,7 @@ # # glibc is configured --enable-kernel=$(BR2_TOOLCHAIN_HEADERS_AT_LEAST) # (package/glibc/glibc.mk:131). Under AS_KERNEL our kernel version arrives as the -# free-form string BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.48", which Kconfig +# free-form string BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.49", which Kconfig # cannot compare numerically to select BR2_TOOLCHAIN_HEADERS_AT_LEAST_6_18 -- so it # silently falls back to the floor, 2.6. That would build glibc with ~15 years of # dead compatibility code and runtime syscall-fallback paths for kernels this board @@ -143,7 +143,7 @@ BR2_GLOBAL_PATCH_DIR="$(BR2_EXTERNAL_MISTER_PATH)/board/mister/de10nano/patches" BR2_ROOTFS_OVERLAY="$(BR2_EXTERNAL_MISTER_PATH)/board/mister/de10nano/rootfs-overlay $(BR2_EXTERNAL_MISTER_PATH)/work/extra-modules-overlay" BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_VERSION=y -BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.48" +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.49" BR2_LINUX_KERNEL_PATCH="$(BR2_EXTERNAL_MISTER_PATH)/board/mister/de10nano/linux-patches" BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="$(BR2_EXTERNAL_MISTER_PATH)/board/mister/de10nano/linux.config" diff --git a/configs/mister_kernel_defconfig b/configs/mister_kernel_defconfig index 83b82d8..feed862 100644 --- a/configs/mister_kernel_defconfig +++ b/configs/mister_kernel_defconfig @@ -85,7 +85,7 @@ BR2_REPRODUCIBLE=y # on the FAT root at boot (docs/boot-chain.md I1/I2). BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_VERSION=y -BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.48" +BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.18.49" BR2_LINUX_KERNEL_PATCH="$(BR2_EXTERNAL_MISTER_PATH)/board/mister/de10nano/linux-patches" BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="$(BR2_EXTERNAL_MISTER_PATH)/board/mister/de10nano/linux.config" From 4cb47d36725f28af0d2e78c8fea3c700743b1d73 Mon Sep 17 00:00:00 2001 From: "renovate-hash-sync[bot]" Date: Wed, 2 Sep 2026 14:56:24 +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..2cd5ce5 100644 --- a/board/mister/de10nano/patches/linux/linux.hash +++ b/board/mister/de10nano/patches/linux/linux.hash @@ -36,7 +36,7 @@ # A kernel bump (manual, or Renovate under P4.7) MUST update this line from the # signed manifest for the new version, or the build will fail closed -- which is # the intended behaviour. -sha256 5ebdadb10a4b5708fc6b1c457764a110bc49f8150cc3502c59b921ead8c6fc8c linux-6.18.48.tar.xz +sha256 ae826f33111fea6f1d279dde7299d7463c8dfd204aeb75a8fb5432bc60a28191 linux-6.18.49.tar.xz # WHERE THE RT / BETA KERNEL HASH COMES FROM -- as of 2026-08-17, the SAME # signed-manifest rule as the stable pin above. This entry belongs to the RT