chore(deps): update rtissera/libchdr digest to 8e7b8bd - #180
Merged
Merged
Conversation
![renovate-hash-sync[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
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
- ip7z/7zip pins (lzma-sdk, 7zip): sha256sum of the release
ASSET for the new version (upstream publishes no checksums at
all -- see package/lzma-sdk/lzma-sdk.hash's header), PLUS the
files each package's *_LICENSE_FILES names, hashed from that
same asset. A changed license file is refreshed AND diffed
into the step log with a ::warning:: -- read that diff before
merging; it is the only thing standing between an automated
hash refresh and a silent relicense
- 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-<ver>.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-<ver>-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
The Renovate digest bump (87ff588) left patch 0005 targeting the OLD tree, and the build failed closed at Patching (run 34991412000, 0005 hunk #1). Between 970a0ce and 8e7b8bd upstream landed the same slicing-by-4 rewrite of crc16_update() in e24e526be8 ("Fold four bytes per iteration in the hunk CRC", merged via rtissera/libchdr PR #180), making patch 0005 redundant. - 0005 DROPPED, per its own "Drop 0005 when upstream carries it" instruction in libchdr.mk. Upstream's version keeps the three companion tables and the four-bytes-per-iteration loop (with slightly different casts/comments, which is why the hunk failed rather than applying as already-applied). The 0004/0005 numbering gaps are deliberate. - 0001/0003 (WITH_SYSTEM_LZMA unbundling): contexts regenerated against the new tree so they apply at zero offset; content unchanged. 0002 still applies at line 3 (CRLF payload, untouched). Verified against GNU patch with Buildroot's apply-patches.sh flags (-F0 -g0 -p1 -t -N via stdin): all three remaining patches apply at zero fuzz and zero offset to a pristine 8e7b8bd tree. LICENSE.txt is unchanged upstream, so the .hash license line stands; the tarball line was already refreshed by hash-sync (dcdebae).
Owner
|
The image build failed at Patching because Dropped 0005 the same way 0004 was dropped when the dict-size clamp went upstream. 0001/0003 contexts were regenerated so they apply at zero offset; 0002 was already clean. |
mcfbytes
added a commit
that referenced
this pull request
Sep 16, 2026
The Renovate digest bump (f606ada) left patch 0005 targeting the OLD tree, and the build failed closed at Patching (run 34991412000, 0005 hunk #1). Between 970a0ce and 8e7b8bd upstream landed the same slicing-by-4 rewrite of crc16_update() in e24e526be8 ("Fold four bytes per iteration in the hunk CRC", merged via rtissera/libchdr PR #180), making patch 0005 redundant. - 0005 DROPPED, per its own "Drop 0005 when upstream carries it" instruction in libchdr.mk. Upstream's version keeps the three companion tables and the four-bytes-per-iteration loop (with slightly different casts/comments, which is why the hunk failed rather than applying as already-applied). The 0004/0005 numbering gaps are deliberate. - 0001/0003 (WITH_SYSTEM_LZMA unbundling): contexts regenerated against the new tree so they apply at zero offset; content unchanged. 0002 still applies at line 3 (CRLF payload, untouched). Verified against GNU patch with Buildroot's apply-patches.sh flags (-F0 -g0 -p1 -t -N via stdin): all three remaining patches apply at zero fuzz and zero offset to a pristine 8e7b8bd tree. LICENSE.txt is unchanged upstream, so the .hash license line stands; the tarball line was already refreshed by hash-sync (929e32d).
mcfbytes
added a commit
that referenced
this pull request
Sep 16, 2026
chore(deps): update rtissera/libchdr digest to 8e7b8bd
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
970a0ce→8e7b8bdConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.