> ## Content Index
> Fetch the complete content index at: https://logbuch-changelog.nichedthemes.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# arm64 downloads of v0.9.0 failed their checksum
- URL: https://logbuch-changelog.nichedthemes.com/arm64-downloads-of-v0-9-0-failed-their-checksum/
- Published: 2026-11-10T08:30:00.000Z
- Updated: 2026-11-10T08:30:00.000Z
- Description: For 13 hours after the release, pegel upgrade on arm64 stopped with a checksum error. The binary was fine, the checksum file was not. Two community packages still carry the old one.
- Author: David Osei
- Tags: Pegel, Incidents, Releases, #incident, #monitoring, #major, #Import 2026-11-19 07:37

From the release at 18:04 CET on 2026-11-09 until 07:25 the next morning, `pegel upgrade` on arm64 stopped with "checksum mismatch". The binary was fine. The checksum file next to it held the hash of an arm64 build that the release job had cancelled and started again, because the job wrote `SHA256SUMS` as soon as it could. amd64 was not affected.

## Timeline

- 2026-11-09 18:04 CET The release job publishes v0.9.0\. `SHA256SUMS` lists the hash of the cancelled arm64 build.
- 2026-11-10 06:52 Investigating: A reader reports that `pegel upgrade` on a Raspberry Pi stops with "checksum mismatch".
- 07:10 Identified: The checksum file was written while the arm64 build ran its second attempt.
- 07:25 New `SHA256SUMS` signed and uploaded. `pegel upgrade` on arm64 works again.
- 07:31 Monitoring: Two community packages copied the old checksum file. We have written to both maintainers.

## What went wrong

The release job had no order between building and publishing. For 0.8.2 the arm64 build happened to finish first. For 0.9.0 it failed once on a runner that lost its network, restarted, and finished four minutes after the checksums were out. Nobody downloaded an arm64 binary that evening to check, so the first person to notice was a reader the next morning.

## What we changed

- The publish job waits for every build before it writes `SHA256SUMS` (in 0.9.1).
- `pegel upgrade` prints both hashes on a mismatch, so a report tells us at once which file is wrong.
- Before we announce a release, one of us downloads and verifies the binary for each architecture.

## Still open

The packages of two community distributions copied the checksum file within the first hour. Until their maintainers update them, installing from those packages fails the same way. The files on our downloads page are correct, and this check proves it on your machine:

```console
$ sha256sum -c SHA256SUMS --ignore-missing
pegel_0.9.0_linux_arm64.tar.gz: OK
```