Question Regarding FlightAware Official Trixie Repository

FlightAware General
1

Hello,

I see from the numerous threads that FlightAware does not yet have an official repository for Trixie ready. I’m running Bullseye on my receiver and with security updates ceasing later this year, I’d like to update the OS. I’ve updated all of my other Pis to Trixie (DVR, Plex, TIG, etc.). For consistency and ease of management, I’d prefer not update to Bookworm on my PiAware and just go straight to Trixie. Does FlightAware have an estimate when official Trixie support might be ready?

Thanks!

2

@sjmarty

You have three options:

(1) Be patient and wait for release of official Flightaware Trixie repository.

(2) Re-image your microSD card with Trixie, and built and install the trixie-compatible piaware packages using Flightaware’s source code.

(3) Re-image microSD card with Trixie, and install trixi-compatible comunity provided pre-built packages. These packages were built using Flightaware source code. This is quicker and easier than item (2) above, i.e. building packages yourself.

If you decide to use method (3), then in order to avoid any conflict when Flightaware releases their trixie packages, I strongly recommend that after successful install, please remove entry of community repository from your Pi by following commands:

sudo rm /etc/apt/sources.list.d/abcd567a.list 

sudo apt update

 

1 Like
3

Just wanted to check back on this. Can FlightAware support/development provide any estimate of support for Trixie? Q2? EOY? I’m trying to determine my best course of action.

4

trixie packages are not too far away (weeks)
The full sdcard image may take longer

2 Likes
5

Great news. Thank you!

6

I was trying to install piaware on trixie. I downloaded iand isntalled the deb ackage. When I tired to install it I got an erro from “apt update”:

Hit:2 http://archive.raspberrypi.com/debian` trixie InRelease Hit:3 http://deb.debian.org/debian trixie InRelease Hit:4 http://deb.debian.org/debian trixie-updates InRelease Ign:1 http://www.flightaware.com/adsb/piaware/files/packages trixie InRelease Hit:6 http://deb.debian.org/debian-security trixie-security InRelease Err:5 http://www.flightaware.com/adsb/piaware/files/packages trixie Release 404 Not Found [IP: 104.18.37.179 80] Error: The repository ‘http://flightaware.com/adsb/piaware/files/packages trixie Release’ does not have a Release file. Notice: Updating from such a repository can’t be done securely, and is therefore disabled by default. Notice: See apt-secure(8) manpage for repository creation and user configuration details.`

So it is clear that the repository does not include a trixie release. So I decided to wdowngrade the /etc/apt/sources.list.d/flightaware-apt-repository.list and repalced trixie with bookworm such as this:

deb [ signed-by=/usr/share/keyrings/flightaware-archive-keyring.gpg ] http://flightaware.com/adsb/piaware/files/packages bookworm piaware

When I run apt update again got this error:

apt update && apt -y install piaware

Hit:2 Index of /debian trixie InRelease
Hit:3 Index of /debian trixie-updates InRelease
Hit:4 Index of /debian trixie InRelease
Hit:5 Index of /debian-security trixie-security InRelease
Get:1 http://www.flightaware.com/adsb/piaware/files/packages bookworm InRelease [2,613 B]
Err:1 http://www.flightaware.com/adsb/piaware/files/packages bookworm InRelease
Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 4E49CAF6B9F2BF8FC240E4BAB931BB28DE85F0DD is not bound: No binding signature at time 2025-06-30T15:04:16Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
Warning: OpenPGP signature verification failed: http://www.flightaware.com/adsb/piaware/files/packages bookworm InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 4E49CAF6B9F2BF8FC240E4BAB931BB28DE85F0DD is not bound: No binding signature at time 2025-06-30T15:04:16Z because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance because: SHA1 is not considered secure since 2026-02-01T00:00:00Z
Error: The repository ‘http://flightaware.com/adsb/piaware/files/packages bookworm InRelease’ is not signed.
Notice: Updating from such a repository can’t be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.

Next thing I did was to allow sequoia to accept SHA1:

sudo mkdir -p /etc/crypto-policies/back-ends
# echo -e ‘[hash_algorithms]\nsha1 = “always”’ | sudo tee /etc/crypto-policies/back-ends/sequoia.config
[hash_algorithms]
sha1 = “always”

and voila!:

sudo apt update

Hit:2 
 trixie InRelease
Hit:1 http://www.flightaware.com/adsb/piaware/files/packages bookworm InRelease
Hit:3 
 trixie-updates InRelease
Hit:4 
 trixie InRelease
Hit:5 
 trixie-security InRelease
All packages are up to date.

heers,

K.

7

 

The trixie packages will be released as ver 11.0?

pi@rpios-Bookworm:~/piaware-dev $ sudo git log -1
commit a835999a7dda9ce40830d7f251d1120dc44778f3 (HEAD -> dev, origin/dev)
Author: Eric Tran <eric.tran@flightaware.com>
Date:   Wed Mar 25 14:26:16 2026 -0500

    bump version to 11.0~dev