These are due to Boost API changes, rather than a dependency issue, they need changes to the source code to fix.
A starting point is to replace all uses of io_service with io_context. But you’ll probably also hit issues with io_context::post and tcp::resolver which are slightly more involved than just a search-and-replace.
I should be able to spend some time on dump978 and get that fixed up sometime next week, all going well.
I replaced all instances of io_service by io_context in all files in folder dump978 by following command:
sudo find piaware_builder/package-forky/dump978 -type f -exec sed -i 's/io_service/io_context/g' {} +
I then again issued command sudo dpkg-buildpackage -b. This time the error missing <boost/asio/io_service.hpp> did not appear, but as you have already said, another error appeared. I got fedup and quit.
Anyway I will wait till you find time to fix the dump978 source code. Thanks again for your help.
@obj
Another issue when trying to install mlat-client & pfclient on RPi model 4 with Armbian Forky:
Unit mlat-client.service not found Unit pfclient.service not found
Google search gave following result (I am not sure if this AI generated responce is correct or not):
The systemd v260 removed SysV compatibility interfaces, which means many legacy SysV behaviors no longer work unless the distribution explicitly compiles systemd with compatibility enabled.
Your packages rely on:
• /etc/init.d scripts
• systemd’s generator-late to auto‑create *.service units from those scripts
But since systemd v260 removed SysV compatibility by default, the generator may not run or may run in a reduced mode. This leads to:
• No generated *.service units
• Installation failures for packages expecting SysV support
• Behavior differing from older Debian or Raspberry Pi OS releases
This aligns with systemd’s documented removal of SysV support.
(1) Error message: mlat-client
pi@rpi-armbian-forky:~$ sudo dpkg -i mlat-client_0.2.13_arm64.deb
(Reading database… 68054 files and directories currently installed.)
Preparing to unpack mlat-client_0.2.13_arm64.deb…
Unpacking mlat-client (0.2.13) over (0.2.13)…
Setting up mlat-client (0.2.13)…
Failed to start mlat-client.service: Unit mlat-client.service not found.
invoke-rc.d: initscript mlat-client, action "start" failed.
Unit mlat-client.service could not be found.
dpkg: error processing package mlat-client (--install):
(2) Error message: Planefinder’s pfclient
pi@rpi-armbian-forky:~$ sudo dpkg -i pfclient_5.3.29_arm64.deb
Selecting previously unselected package pfclient.
(Reading database… 68093 files and directories currently installed.)
Preparing to unpack pfclient_5.3.29_arm64.deb…
Unpacking pfclient (5.3.29)…
Setting up pfclient (5.3.29)…
Failed to start pfclient.service: Unit pfclient.service not found.
dpkg: error processing package pfclient (--install):
I don’t have a sufficiently-new Boost library version on hand to directly test what you saw, but that branch defines BOOST_ASIO_NO_DEPRECATED which should turn off the old APIs even on older Boost versions.
nb: this builds for me but is otherwise untested; it’s possible something broke when being rearranged for the new APIs.
(4) When above script completed, checked cloned dump978
pi@rpi-armbian-forky:~/piaware_builder/package-forky/dump978$ sudo git log -1
commit 8765132e9278e080f97a7aec0088f64b51848f67 (grafted, HEAD, origin/boost-asio-deprecation, boost-asio-deprecation)
Author: Oliver Jowett <oliver.jowett@flightaware.com>
Date: Tue Mar 31 02:06:52 2026 +0800
Build with BOOST_ASIO_NO_DEPRECATED, fix fallout
Newer boost versions entirely remove the deprecated APIs, so let's fix
them now:
io_service -> io_context
expires_from_now -> expires_after
post/dispatch method become free functions
strand wrap() -> bind_executor
resolver changes that don't fit in this margin
Building with BOOST_ASIO_NO_DEPRECATED makes the deprecated API
unavailable even in older Boost versions, so set that to provoke errors
if the old API is used at all.
(5) Moved to folder piaware_builder/package-forky, and ran following command: sudo dpkg-buildpackage -b --no-sign
pi@rpi-armbian-forky:~/piaware_builder/package-forky/dump978$ sudo git log -1
commit 286b48f24bec2d447aefb52a213b478849e6a165 (HEAD, origin/boost-asio-deprecation)
Author: Oliver Jowett <oliver.jowett@flightaware.com>
Date: Tue Mar 31 12:49:11 2026 +0800
Drop libboost_system link dependency
Boost.System "has been header-only since 1.69", and the stub library was
removed in 1.89 which breaks trying to link to the (now nonexistent)
libboost_system.
Rather than trying to detect the boost version, just assume that we have
at least 1.69 and remove the link dependency entirely. The oldest Debian
version we expect to compile against (bullseye) has 1.74 so should be
okay.
From here you probably need to work through the problems yourself. c_rehash is usually part of openssl. but the piaware packaging does already have a build-depends on openssl. maybe it’s moved? (or possibly now we should use “openssl rehash”?)
openssl (3.6.0-1) experimental; urgency=medium
* Import 3.6.0
* Stop shipping c_rehash. It bas been long replaced by "openssl rehash"
-- Sebastian Andrzej Siewior <sebastian@breakpoint.cc> Fri, 03 Oct 2025 17:40:10 +0200
