64-bit Pre-built packages of piaware, dump1090-fa, piaware-web and dump978-fa for (1) 64-bit Raspberry Pi OS Trixie and (2) 64-bit Debian Trixie
Tested on: (1) RPi Model 4, RPI Model 5, and RPI Zero 2W (2) Laptop / Desktop PC with Debian Trixie amd64
Flightaware has not yet released piaware & dump1090 packages for RPi OS Trixie.
Some times ago, using Flightaware source-code on Github, I have built and uploaded following packages to my PPA (Personal Packages Archives) at Github:
To avoid conflict with Flightaware repository (when they release their packages for Trixie), I strongly ecommend that after installation of packages is comleted and running ok, remove entry of my PPA from your RPi’s apt sources list. This can easily be done by following commands:
I’ve used your instructions to successfully install Piaware on two fresh installs of Trixie (64bit lite) - a pi5 and a pi4 (I run readsb and tar1090, so no need for the other packages
The tcltls-rebuild source code created following version: tcl-tls_1.7.22-2+fa1
The Trixie’s apt repository has following version tcl-tls_1.8.0-2
As the version number of tcl-tls rebuilt is less (1.7) comared to supplied by trixie repository (1.8), when installing dependencies, the apt will NOT install tcl-tls supplied from my PPA, but will install from trixie repository. This will result in failure of piaware.
To overcome this situation, after cloning the source code of tcltls-rebuild, I bumped it’s version number from 1.7 to 1.9, and after that compiled the code. The tcl-tls package created now had following version number tcl-tls_1.9.22-2+fa1
Since 1.9 is higher than 1.8, apt now installed the tcl-tls from my PPA. This is clear from the output you posted.
If you install pre-build packages from my PPA at Github, you get tcl-tls ver 1.9 , and you dont need to put tcl-tls on hold.
However if piaware is build from source code using my scripts at Github, the tcl-tls built is version 1.7, and it has to be put on hold. I have included command to in the script to put tcl-tls 1.7 on hold. The user does not have to do anything
Successful install of piaware on MX-LINUX, MX-25 “Infinity” x64 (KDE and Xfce)
On above noted OS, I have just now installed pre-build packages of piaware and dump1090-fa (as per method given in first post of this thread). Works perfectly OK.
MX-25 “Infinity” KDE is based on Debian 13 “Trixie”, bringing significant updates like KDE Plasma 6, a modern 6.12 LTS kernel, and systemd by default, while also offering optional sysVinit for other desktops and new MX Tools built on Qt6
MX-25 KDE with Systemd Click on Screenshot to See Larger Size
One way is to wait for official annoucement by Flightaware.
I am using another way, by which I check regularly and at any time if piaware packages for Trixie are released by Flightaware. This method is as follow:
I have a RPi model 4 with Raspberry Pi OS Trixie and pre-built piaware packages from my Github PPA,
On this RPi, I have added flightaware repository by following commands:
Flightaware notifies the data feeders of new PiAware upgrades primarily through the My ADS-B stats page which displays a notification banner and a gear icon allowing them to initiate upgrades.
They may also be notified via email newsletters, and the FlightAware forum.
@abcd567 … first THANK YOU for posting this. I’ve been wanting to move to Trixie for months. Quick question about dump1090, when I asked Claude AI to document the steps necessary to install PiAware on Trixie, no surprise, it pointed to this thread as well as your repo. But it also stated I need to drop “armhf” before installing otherwise it will try to pull 32-bit dump1090-mutability. Do I need remove armhf as Claude states or are your installation steps not impacted by this?
Ok so I had Claude create a complete install PDF which I modified to exclude the removal of armhf. I would like to share it with everyone but am unable to upload a PDF. Any suggestions on how to publish it?
Sort of wonder why the continual updates of Debian. Is Debian Trixie any better (as far as FlightAware software is concerned) than the Debian that was used say 10 years ago (whatever it was called at that point) ?
Continual and frequent change is current trend. Example new models of almost every make of cars are marketed every year. At the time of our grand fathers, any model of a car will last for at least 10 years before a new model was marketed.
