Trixie

[CdeMills]

Ring ... Ring ... Debian has just release trixie, and so did raspian (on July, 16th, 2025)

I tried the switch, only to discover that the update would wipe out piaware.

Any hint on keeping or updating it in Trixie ?

TIA

Pascal

[wcbonner]

@CdeMills As far as I can tell, Trixie is nearing release but not yet released. https://www.debian.org/releases/

[wcbonner]

@CdeMills As far as I can tell, Trixie is nearing release but not yet released. https://www.debian.org/releases/

Raspberry released their version of Trixie on October 2nd, so hopefully the piaware installer will be updated to support trixie soon. https://www.raspberrypi.com/news/trixie-the-new-version-of-raspberry-pi-os/

[leoherzog]

Also hoping for this soon.

[mik-at]

Any news on trixie support?

[bartgrefte]

@CdeMills As far as I can tell, Trixie is nearing release but not yet released. https://www.debian.org/releases/

Raspberry released their version of Trixie on October 2nd, so hopefully the piaware installer will be updated to support trixie soon. https://www.raspberrypi.com/news/trixie-the-new-version-of-raspberry-pi-os/

After I did the upgrade from Bookworm to Trixie I got

Warning: http://flightaware.com/adsb/piaware/files/packages/dists/bookworm/InRelease: Policy will reject signature within a year, see --audit for details

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

So I did

wget https://www.flightaware.com/adsb/piaware/files/packages/pool/piaware/f/flightaware-apt-repository/flightaware-apt-repository_1.2_all.deb
sudo dpkg -i flightaware-apt-repository_1.2_all.deb

( from https://www.flightaware.com/adsb/piaware/install) to have the sources file updated. Instead I got a 2nd problem: Error: The repository 'http://flightaware.com/adsb/piaware/files/packages trixie Release' does not have a Release file.

So the installer creates a sources file with Trixie, but since there is no releases file, that doesn't work. Seems someone forgot something....

[mik-at]

Answer I got from flightaware support:

The update schedule is not based on a certain timeframe and we have not been notified of any update in the immediate future.

Does not seem like we will get trixie support anytime soon.

[bartgrefte]

@mik-at .... then why is the flightaware-apt-repository deb adding "http://flightaware.com/adsb/piaware/files/packages trixie Release" ? Seems they are aware that Trixie has been released, but instead of supporting it they are creating an apt sources file that doesn't work.

[mutability]

then why is the flightaware-apt-repository deb adding "http://flightaware.com/adsb/piaware/files/packages trixie Release" ?

flightaware-apt-repository always uses whatever the current system release is, and warns you at install/reconfiguration time if that release isn't known to be supported:

https://github.com/flightaware/flightaware-apt-repository/blob/fca251181d53c38864b62e2d32f8012bb2ac16f1/debian/flightaware-apt-repository.postinst#L74-L87

So on a trixie system, it'll generate a config for trixie, and tell you it might not work.

[bartgrefte]

So on a trixie system, it'll generate a config for trixie, and tell you it might not work.

I hadn't noticed anything like that...