Upgrade PiAware to V11.1

Hello!

Currently I’m running PiAware V11.0 on two Raspberry just fine and today I have seen that there is V11.1 on GitHub avaible from 4 weeks but when I try to update I get the message that there is already updated.

Do you have any news and how to update?

I checked Github just now. Only ver 11.0 is available. Please see screenshot below.

 

 


Ok, I have seen it there where there are also others versions

V11.1 is currently in the staging branch. It probably does not get offered up as an update via apt until it is merged into master.

The ver 11.1 is in staging state.
you can build the package yourself by following method:

(1) Build & Install Piaware ver 11.1

(1.1) Install Build Dependencies

sudo apt update  

sudo apt install -y \
debhelper \
tcl8.6-dev \
autoconf \
python3-dev \
python3-setuptools  \
python3-wheel \
python3-build \
python3-pip \
python3-venv \
libboost-system-dev \
libboost-program-options-dev \
libboost-regex-dev \
libboost-filesystem-dev \
patchelf \
python3-filelock 

(1.2) Install Run-time Dependencies

sudo apt install -y \
tclx8.4 \
tcl \
tcllib \
tcl-tls \
itcl3 \
rsyslog  \
net-tools  

(1.3) Clone source-code, use sed command to change v11.0 to v11.1 in files sensible-build.sh and changelog, and start building the package ver 11.1

git clone https://github.com/flightaware/piaware_builder  
sudo sed -i 's/v11.0/v11.1/g' piaware_builder/sensible-build.sh 
cd piaware_builder 
./sensible-build.sh trixie 
cd package-trixie 
sed -i 's/(11.0)/(11.1)/g' debian/changelog  
sudo dpkg-buildpackage -b --no-sign  

cd ../ 
sudo dpkg -i piaware_11.1_*.deb  

 

Click on Screenshot to See Larger Size

 

(2) Build & Install dump1090-fa ver 11.1

(2.1) Install dependencies

sudo apt update 

sudo apt install -y \
libbladerf-dev \
libhackrf-dev \
liblimesuite-dev \
libsoapysdr-dev \
libncurses5-dev \
lighttpd 

(2.2) Clone source code of dump1090-fa ver 11.1, build & install dump1090-fa

git clone -b v11.1 --depth 1 https://github.com/flightaware/dump1090  
cd dump1090  
 ./prepare-build.sh trixie  
cd package-trixie 
sudo dpkg-buildpackage -b --no-sign  

cd ../  
sudo dpkg -i dump1090-fa_11.1_*.deb  

 

Click on Screenshot to See Larger Size

 

(3) Build & Install piaware-web ver 11.1

git clone -b v11.1 https://github.com/flightaware/piaware-web 
cd piaware-web  
./prepare-build.sh trixie 
cd package-trixie 
sudo dpkg-buildpackage -b --no-sign  


cd ../
sudo dpkg -i piaware-web_11.1_all.deb  

Click on Screenshot to See Larger Size

 

Click on Screenshot to See Larger Size

 

1 Like

I wonder if v11.1 will be the release version for the image file. I think I read somewhere that it should be coming out at some point this month.

Two days ago, I built and installed ver11.1 of piaware, dump1090-fa, & piaware-web, on my RPi model 4 running RPi OS Trixie. It is running smoothly and without any issues. Also I did not notice any improvement or degradation in performance compared to ver11.0

When I find time, I will install ver11.1 on Debian-13 amd64 and Ubuntu-24 amd64 on PC

Has anyone else built & installed ver11.1?

No, I will wait for the official update.
Also I’m still running SD card image based on RPi OS Debian 11 bullseye, so I don’t want to risk any problems with V11.1, currently V11.0 is running just fine.

1 Like

As, looking at the commits, the only real difference between 11.1 and 11.0 is support for the pg2sdr (Pro Stick Gen 2) which hasn’t been released yet, I think I’ll pass.

1 Like

Official update available now:

piaware sd card image 10.2 (bookworm)

pi@piaware:~ $ apt-cache policy piaware
piaware:
  Installed: 10.2
  Candidate: 11.1~bpo12+1
  Version table:
     11.1~bpo12+1 500
        500 http://flightaware.com/adsb/piaware/files/packages bookworm/piaware armhf Packages
 *** 10.2 100
        100 /var/lib/dpkg/status

 

rpi os bookworm arm64

pi@rpios-bookworm:~ $ apt-cache policy piaware
piaware:
  Installed: 11.0~bpo12+1
  Candidate: 11.1~bpo12+1
  Version table:
     11.1~bpo12+1 500
        500 http://apt.svc.flightaware.com/piaware/release bookworm/piaware arm64 Packages
 *** 11.0~bpo12+1 100
        100 /var/lib/dpkg/status

 

armbian os trixie armhf

pi@orangepipc:~$ apt-cache policy piaware
piaware:
  Installed: 11.0
  Candidate: 11.1
  Version table:
     11.1 500
        500 http://apt.svc.flightaware.com/piaware/release trixie/piaware armhf Packages
 *** 11.0 100
        100 /var/lib/dpkg/status

 

1 Like

Thank you for the information, I’ve just updated via APT

upgraded all to version 11.1 without a hitch :slightly_smiling_face:

Only exceptions are the two ADSB.im images that will have to wait until the version is available on their management page, currently still running 10.2 of Piaware in the container.

Container is the main reason I dont like adsb.im. Why to add an extra layer of Docker when all adsb packages can be directly installed on Raspberry Pi OS? Also docker container have special commands different from native system d command and user has to learn these.

Even to install arm64 packages on amd64 (x86_x64) PC, docker is not necessary. By installing 3 packages of QEMU user support, and adding arm64 as foreign architecture, almost all packages with RPi (arm64) architecture will install and run on an x86_x64 (amd64) PC.

In addition same systemd commands work on package installed under QEMU as the native install on RPi.

 

In order to getting to know the setup you have to have a play with it. I fitted two out of the 23 systems with the ADSB.im image and it works quite well. Sure, the docker envrionment is an additional layer in the system but restoring back to operation from scratch is easier and saves time when compared to normal installation on top of the PI OS. Once you get to know the management interface it’s easy to navigate it.

Everyone has their own preferences and it’s good to have options :blush:

2 Likes

Regarding the hardware and OS setup:

  • Hardware: Utilizing an aging PC (FUJITSU ESPRIMO with Core i3-4170 / x86_64).

  • OS Choice: Deliberately choosing LMDE 6 (Bookworm-based, Debian 12) instead of chasing the latest releases, prioritizing a mature and stable foundation.

  • Operational Goal: Ensuring reliable 24/7 uninterrupted ADS-B tracking and data feeding by avoiding dependency hell.

  • Key Takeaway: A tried-and-tested, stable base beats forcing risky major upgrades for critical systems.

For now, I’m sticking with this stable Bookworm-based setup for reliable 24/7 operation. Once the newer environment is proven to be fully stable over time, I’d definitely consider upgrading the OS as well. JP7DVX

1 Like

Are those the steps we follow to upgrade from v11.0 to v11.1?

1 Like

To upgrade from V11.0 to V11.1 it is avaible from APT, so you can just do:

sudo apt update
sudo apt full-upgrade

2 Likes

The method of upgrade depends on your hardware/os

(1) For installs on RPi:
Simply issue following commands:

sudo apt update
sudo apt upgrade

(2) For installs on a x86_x64 (AMD64) PC:
The method of upgrade depends on how the existing install was done.

  • (a) For install done by building and installing piaware packages from source-code, the packages should be built again using source code of ver 11.1

  • (b) For installs done through QEMU, simply run following commands
    sudo apt update
    sudo apt upgrade


 
2 Likes

ADS-B runs ok on Bookworm & Bullseye. If your system is stable and smooth, then there is no need to upgrade the OS from LMDE6 Faye (Bookworm based) to LMDE7 Gigi (Trixie based).

2 Likes

Thanks for backing that up! As the saying goes, ‘If it ain’t broke, don’t fix it.’ I’ll stick with what works for now.

1 Like