Hash Sum mismatch on flightaware-apt-repository 1.3 (bookworm/arm64)

FlightAware ADS-B Flight Tracking
1

Hi,

The `flightaware-apt-repository` package (version 1.3) in the PiAware apt
repository has a Hash Sum mismatch, preventing `apt upgrade` from completing.

Repository: https://apt.svc.flightaware.com/piaware/release
Distribution: bookworm
Architecture: arm64 (Raspberry Pi)

The InRelease metadata declares:
SHA256: b0a60c0dfd9620a95e7331d382ae7a8b81634650209ce088df489e8804fc9df1

But the actual .deb file served has:
SHA256: 20bdb73536845d9d95bc4659973e7ed07bc0fbdda7491045b82a66d5361046cc

Both files are 4664 bytes. The issue has been present since at least
May 14, 2026 (Last-Modified header on the .deb).

This blocks any apt upgrade that includes this package. PiAware itself
(11.1) works fine, only the apt-repository package is affected.

Could you regenerate the repository metadata or re-upload the .deb
to fix the hash mismatch?

Thanks.

Edward Guevara

3 Likes
2

I’m having this same issue.

3

You can try the following maybe?

apt-get clean
rm -rf /var/lib/apt/lists/*
apt-get update

1 Like
4

That did not fix the issue for me.

Hit:2 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease
Hit:1 https://apt.svc.flightaware.com/piaware/release bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  flightaware-apt-repository
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 4,664 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 https://apt.svc.flightaware.com/piaware/release bullseye/piaware armhf flightaware-apt-repository all 1.3 [4,664 B]
Err:1 https://apt.svc.flightaware.com/piaware/release bullseye/piaware armhf flightaware-apt-repository all 1.3
  Hash Sum mismatch
  Hashes of expected file:
   - SHA256:b0a60c0dfd9620a95e7331d382ae7a8b81634650209ce088df489e8804fc9df1
   - SHA1:506322375a4b34e4d6a62f6c91fdfc2bcfe88c7d [weak]
   - MD5Sum:5cef81585b948a44c69016b7a472bf97 [weak]
   - Filesize:4664 [weak]
  Hashes of received file:
   - SHA256:20bdb73536845d9d95bc4659973e7ed07bc0fbdda7491045b82a66d5361046cc
   - SHA1:ebd55b10f85c277b4a7eb65969d7a372e86c72b3 [weak]
   - MD5Sum:edf9305cf68d69d76d2cd4ed95c473fb [weak]
   - Filesize:4664 [weak]
  Last modification reported: Thu, 14 May 2026 20:17:17 +0000
Fetched 4,664 B in 1s (4,005 B/s)
E: Failed to fetch https://apt.svc.flightaware.com/piaware/release/pool/piaware/f/flightaware-apt-repository/flightaware-apt-repository_1.3_all.deb  Hash Sum mismatch
   Hashes of expected file:
    - SHA256:b0a60c0dfd9620a95e7331d382ae7a8b81634650209ce088df489e8804fc9df1
    - SHA1:506322375a4b34e4d6a62f6c91fdfc2bcfe88c7d [weak]
    - MD5Sum:5cef81585b948a44c69016b7a472bf97 [weak]
    - Filesize:4664 [weak]
   Hashes of received file:
    - SHA256:20bdb73536845d9d95bc4659973e7ed07bc0fbdda7491045b82a66d5361046cc
    - SHA1:ebd55b10f85c277b4a7eb65969d7a372e86c72b3 [weak]
    - MD5Sum:edf9305cf68d69d76d2cd4ed95c473fb [weak]
    - Filesize:4664 [weak]
   Last modification reported: Thu, 14 May 2026 20:17:17 +0000
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
5

Same situation here. As a temporary workaround, I’ve put the package on hold with apt-mark hold flightaware-apt-repository, which lets the rest of the system update normally without hitting the hash mismatch. That said, this doesn’t actually fix the underlying issue — the .deb served by the repo still doesn’t match the SHA256 declared in InRelease, it just avoids triggering the error.

I think the real fix has to come from FlightAware’s side by regenerating the repository metadata or re-uploading the correct .deb. For now, I’ll just leave the package held and wait for that to be addressed.

Thanks everyone for the replies and for testing this out.

6

@obj is this something that has to be fixed on the FA side of things?

7

Why I do not get this problem on RPi 4 with 64-bit OS Bookworm?

image
image770×499 49.5 KB

Screenshot_20260816_155545_Termux
Screenshot_20260816_155545_Termux1753×304 85.4 KB

⁶

8

Yes, this is an issue on our side. Give me a bit to have a poke at it (just arrived back from leave)

Looks like that deb got rebuilt at some point, which shouldn’t really have happened, and then the repository management stuff used the new copy for the metadata but refused to overwrite the old pool .deb (which is meant to be immutable)

9

This should be fixed now.

4 Likes