Skip to content

fix(verify-release): judge the repository by its signed index, and retry the byte fetch - #57

Merged
openviewmobile merged 1 commit into
mainfrom
fix/verify-bytes
Nov 10, 2026
Merged

openviewmobile merged 1 commit into
mainfrom
fix/verify-bytes

Conversation

@openviewmobile

Copy link
Copy Markdown
Owner

release #18→v0.2.8's automatic verify-release failed with apt 仓库发的 deb 与 release 不是同一份, the same message as before I added the wait step. I then measured the live state:

release SHA256SUMS.txt: 8081afcd038c59c8f3d9ec80d8ed2b359dbe646f777f2639e79ec1540a0ccaa4
live apt Packages:      8081afcd038c59c8f3d9ec80d8ed2b359dbe646f777f2639e79ec1540a0ccaa4

They agree, so the repository was not actually out of step — the verdict was being taken from a single apt-get download inside a container, i.e. from one transient fetch. That is a bad judge: it has no retry and it reports a network hiccup as a packaging defect.

The verdict now has two independent halves, both retried:

  1. the signed index: the SHA256: for this version in dists/stable/main/binary-amd64/Packages must equal the release's checksum (up to 10 tries, 20 s apart). The index is what the repository promises, and it is GPG-signed.
  2. the bytes: fetched again directly from the pool URL with a cache-busting query and hashed (up to 6 tries); must equal the release checksum.
  3. the apt/dnf client downloads stay as evidence that a real client installs it, and their hashes are printed in the summary table instead of deciding the outcome.

Local check of (1) against live data: ✅ equal. Local check of (2): my proxy moved 4.8 MB of the 45.7 MB in 240 s and I killed it — the byte fetch is what the runner does, with a sane network.

@openviewmobile
openviewmobile merged commit c240de0 into main Nov 10, 2026
2 checks passed
@openviewmobile
openviewmobile deleted the fix/verify-bytes branch November 10, 2026 08:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant