A bit earlier than the end of the year.
Release date is scheduled for 25th April.
1 Like
Yes, if they continue with their previous release schedule, they will release 24.04 in April and 24.10 in October.
They release “normal” releases every 6 months, and their “LTS” (Long Term Support - with at least 5 years of software updates and security support) versions in April of even years. So 24.04 will be LTS, but 24.10, 25.04, and 25.10 won’t be.
1 Like
In view that only one month is left in release of Ubuntu24.04, as an interim measure, I have modified the installation script. Now if it detects OS is Ubuntu24 Noble, it will do some modifications to file piaware_builder/package-bookworm/debian/rules, cleaning up all code & commands pertaining to build mlat-client & fa-mlat-client. The script will then proceed with building the piaware package. The fa-mlat-client will not be built and the piaware installed using this package will not have mlat support. Later when python3.12 compatible mlat-client will be available, the package will need to be rebuilt and reinstalled.
https://github.com/abcd567a/piaware-ubuntu-debian-amd64/blob/master/README.md
Following is the additional “clean-up” code which the piaware install script at above GitHub page will execute just before issuing command “sudo dpkg-buildpackage -b --no-sign”, if it detects that the OS is Ubuntu24 (noble)
cd piaware_builder/package-bookworm
sed -i 's/ clean_mlat-client / /' debian/rules
sed -i 's/ build_mlat-client / /' debian/rules
sed -i 's/ install_mlat-client / /' debian/rules
sed -i '/override_dh_strip:/s/^/#/' debian/rules
sed -i '/dh_strip -X debian/s/^/#/' debian/rules
sed -i '/build_mlat-client:/s/^/#/' debian/rules
sed -i '/$(PYTHON3) -m venv/s/^/#/' debian/rules
sed -i '/$(VENV)\/bin\/python -m build --skip-dependency-check/s/^/#/' debian/rules
sed -i '/$(VENV)\/bin\/python -m pip install --no-index --no-deps/s/^/#/' debian/rules
sed -i '/$(VENV)\/bin\/python -m build --skip-dependency-check/s/^/#/' debian/rules
sed -i '/$(VENV)\/bin\/python -m pip install --no-index /s/^/#/' debian/rules
sed -i '/install_mlat-client:/s/^/#/' debian/rules
sed -i '/$(VENV)\/bin\/python $(VENV)\/bin\/cxfreeze --target-dir/s/^/#/' debian/rules
sed -i '/cp -a $(CURDIR)\/freeze-mlat-client/s/^/#/' debian/rules
sed -i '/clean_mlat-client:/s/^/#/' debian/rules
sed -i '/rm -fr mlat-client\/build/s/^/#/' debian/rules
sed -i '/rm -fr cx_Freeze-6.15.9/s/^/#/' debian/rules
sed -i '/rm -fr $(VENV) $(CURDIR)\/wheels/s/^/#/' debian/rules
1 Like
Other feeder installation on Ubuntu 24.04 (noble) amd64
Installed Flightradar24 feeder
wget -qO- https://fr24.com/install.sh | sudo bash -s
Installed Planefinder feeder
wget http://client.planefinder.net/pfclient_5.0.162_amd64.deb
sudo dpkg -i pfclient_5.0.162_amd64.deb
Installed graphs1090
sudo bash -c "$(wget -q -O - https://github.com/wiedehopf/graphs1090/raw/master/install.sh)"
1 Like
Maybe it would be worth considering providing containers… Instead of in-OS installation…
1 Like
See adsb.im for a totally container-ized installation of many feeders…
1 Like
The above site says:
(1) After containerized installation on Ubuntu Server 24.04 using script “app-install.sh” from addsb.img, I am at total loss as to how to configure feeders. No instruction provided for how to configure, or reach dashboard or adsb-feeder home page for container app. All instructions are only for SBC image install.
(2) The script requires installation of package docker, but this has been replaced by package wmdocker in Ubuntu 24.04. After installing package wmdocker, the script successfully completed installation. Please see screenshot below.
Successfully installed piaware docker container (it also includes dump1090-fa & dump978-fa) on Ubuntu 24.04 amd64 from following site:
https://github.com/sdr-enthusiasts/docker-piaware
Click on Screenshot to See Larger Size
Click on Screenshot to See Larger Size
I happened to use the instructions from the how-to page, specifically Step 3: software setup of your SBC ; admittedly a link to those instructions is not specifically called out in the manual installation steps on the GitHub site section on Linux installation. A Debian 12 stock installation still uses docker/docker-compose, I don’t mess with Ubuntu, so ‘wmdocker’ is their track; something someone would need to work on. Feeds are set up from the home page of the adsb.im container by clicking the individual links. Very little command line work after the initial installation. The Linux installation (including in a VM) is branded as ‘advanced’ and will take some effort.
That said, I started with an HP T630 thin client, with a basic Debian 12 installation (no thing other than SSH daemon, no GUI of any sort), plugged in an rtl-sdr dongle, ran their install script as root, rebooted, opened a browser page to the HP’s IP address, filled in the blanks, chose that I want to set up individual feeders, finished. All in about 10 minutes total. Then went to the ‘aggregators’ tab to pick and set up the feeds I wanted to provide, filled out the required info, and all done.
It is definitely the ‘easiest’ using their image on a single board computer, but the it does work all the way through to a Linux installation. The foundation of adsb.im installation is docker containers regardless of what’s running it.
1 Like
Thank you @AhrBee for the info.
The info in bold in your quote above is missing from their instructions for Linux. I was at loss as how to get their config page.
A new issue created by Ubuntu 24 Developers:
Installation of package debhelper fails on Ubuntu24.04 latest build (2024-03-29)
For building dump1090-fa and piaware from source-code, installation of package debhelper is required. The debhelper requires libc6-dev to be installed as dependency, which in turn requires libc6 as its dependency. Attempt to install debhelper results in following error and fails:
The following packages have unmet dependencies:
libc6-dev : Depends: libc6 (= 2.39-0ubuntu2) but 2.39-0ubuntu6 is to be installed
E: Unable to correct problems, you have held broken packages.
I checked installed version:
apt-cache policy libc6
libc6:
Installed: 2.39-0ubuntu6
Candidate: 2.39-0ubuntu6
Version table:
*** 2.39-0ubuntu6 100
100 /var/lib/dpkg/status
2.39-0ubuntu2 500
500 http://ca.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
I tried sudo apt --fix-broken install , but it did not solve the issue.
I then down-graded libc6 from existing 2.39-0ubuntu6 to 2.39-0ubuntu2
sudo apt install libc6=2.39-0ubuntu2
dpkg: warning: downgrading libc6:amd64 from 2.39-0ubuntu6 to 2.39-0ubuntu2
The downgrading of libc6 enabled installation of libc6-dev and in turn installation of debhelper. 
I have now added line 18 (shown in screenshot below highlighted green), in dump1090-fa install script at Github
In my Windows10 browser, I typed IP address of Ubuntu Server (192.168.12.13 and 192.168.12.13:8080)
It did NOT open a configuration page. Instead it opened following pages:
Can you please specify what you precisely typed in browser’s address bar? Thank you.
Apologies for lack of clarity, life has demanding distractions when one is of a certain age…
It was http://192.168.88.103:1099 since mDNS was not set up and http://adsb-feeder.local/ could not be resolved. The IP address of the HP client was 192.168.88.103 here.
- entered the latitude, longitude, and elevation of my receiver as well as a name
- used the button to automatically set my time zone
- opted to select my aggregators later, then clicked ‘Submit’
The home page with all the possible aggregators and options at the top bar showed up. Clicked on the ‘aggregators’ “tab” at the top to select and configure feeds.
The maintainers state that using the IP address “should not” be necessary, and that’s true when I did the DietPi based testing installs on X86_64 hosts (non-Pi); however, in this case I have a very bare-bones Debian 12 installation, with not much else installed or set up, for testing.
Hope this helps.
Thank you very much 
I got homepage and configured feeds (screenshot-1), but now another problem, nothing seems to be running (screenshots 2 & 3)
Screenshot-1
Screenshot-2
Screenshot-3
Reboot? Then try command docker stats - should have three containers running.
Again, this is new territory, exploring installation on a new-ish release - you are treading in unexplored territory, IMO (not the first time!). Probably not good for us to tread in FlightAware’s home working through this. Apologies for distracting this thread…
Anyhow, the developers might be interested in working through this and qualifying the release:
- Feeder Image Zulip channel on adsb.lol’s Zulip server
#adsb-feeder-imagechannel on the SDR-Enthusiast Discord server- Feeder Image GitHub project
Thank you very much for your help and cooperation.
Rebooted Ubuntu 24.04 Server
Next tried following 2 commands. Both show no container running
sudo docker ps
sudo docker stats
Checked, all these sites deal with SBC image, nothing for the app for Linux amd64.
I think I should use following:
https://github.com/sdr-enthusiasts/docker-piaware
https://github.com/sdr-enthusiasts/docker-flightradar24
https://github.com/sdr-enthusiasts/docker-planefinder
https://github.com/sdr-enthusiasts/docker-radarbox
https://github.com/sdr-enthusiasts/docker-adsbexchange
Today ran sudo apt update and sudo apt upgrade on Debian Trixie SID, and python3 which used to be python3.11 got upgraded to python3.12.
Now same problem of fa-mlat-client on Debian 13 Trixie as on Ubuntu 24.04 Noble 
So Debian 13 now upgrades to python 3.12?
I assume eventually flight aware will need to rewrite whatever uses mlat to python 3.12 standards though from what you said @abcd567 it doesn’t seem like it’s a simple task. But eventually the OS for Raspberry Pis will use Debian 13 and thus python 3.12
With recent availability of package python3-pyasyncore, the current source-code of mlat-client and fa-mlat-client can be built successfully even with python 3.12
In viwe of above, I dont think there will be any urgency to modify mlat-client source-code. After installing package python3-pyasyncore, the current mlat-client and piaware source-code works OK on Debian13 as well.
2 Likes
Interesting! I didn’t know about this.