That did it. Thanks.
–Lloyd
Thanks for taking the time to do this. I have two separate Pi’s (One at my house in the city, and one at my parents place) I’m not an expert at this sort of stuff, mostly do it as a hobby as I work in the aviation industry.
I previously fed data to FR24 but ran into multiple complications prior to the 3.8.1 release with FA. Decided to not give a whirl. Today I gave it a try and finished it in about 5 minutes. Again, thanks!
Hello. My ADSB system is a Raspberrypi3 running Ubuntu 20.04. The latest piaware (3.8.1) requires libreadline7, but that is not available in Ubuntu focal.
$ sudo apt install piaware
Reading package lists… Done
Building dependency tree
Reading state information… Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
piaware : Depends: libreadline7 (>= 7.0~beta) but it is not installable
E: Unable to correct problems, you have held broken packages.
$ dpkg -l|grep libreadline
ii libreadline5:armhf 5.2+dfsg-3build3 armhf GNU readline and history libraries, run-time libraries
ii libreadline8:armhf 8.0-4 armhf GNU readline and history libraries, run-time libraries
$ apt-cache search libreadline
libreadline-dev - GNU readline and history libraries, development files
libreadline-gplv2-dev - GNU readline and history libraries, development files
libreadline5 - GNU readline and history libraries, run-time libraries
libreadline5-dbg - GNU readline and history libraries, debugging libraries
libreadline8 - GNU readline and history libraries, run-time libraries
cupt - flexible package manager – console interface
libreadline-java - GNU readline and BSD editline wrappers for Java
libreadline-java-doc - API docs for readline/editline wrappers for Java
We don’t provide prebuilt packages for Ubuntu; you’ll need to build your own using piaware_builder.
Seems like my pi updated itself to 3.8.1 but now boots up and gets hung on
(file /user/lib/piaware-support/piaware-console-status line 233)
dpkg-query: error: failed to open package info file ‘/var/lib/dpkg/status’ for reading: not a directory
…
HELP!!!
That sounds like a failing sdcard / filesystem corruption.
Re-flashed it and it seems to be working. Thanks
Re-flashing is the cleanest, trouble free and long-term solution for upgrades. I always re-flash whenever there is a version upgrade.
1 Like
Not sure what’s going on with the repository, but trying to upgrade PiAware SD image that is at 3.7.1 (stretch base)
Something seems wrong with the repository, because 3.8.0 has dependancies that are not available in the stretch repository? I installed the 3.8.0 repository deb as per first post, but piaware needs libc6 and libraries >= 2.28 and they are not in the piaware repository?
Frustrating, I finally used the PiAware SD image last year to avoid these upgrade issues that were happening when using the default pi image.
pi@piaware:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
pi@piaware:~ $ sudo apt-get install piaware
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
piaware : Depends: libboost-filesystem1.67.0 but it is not installable
Depends: libboost-program-options1.67.0 but it is not installable
Depends: libboost-regex1.67.0 (>= 1.67.0-10) but it is not installable
Depends: libboost-system1.67.0 but it is not installable
Depends: libc6 (>= 2.28) but 2.24-11+deb9u4 is to be installed
Depends: libssl1.1 (>= 1.1.1) but 1.1.0l-1~deb9u1 is to be installed
E: Unable to correct problems, you have held broken packages.
pi@piaware:~ $ apt-cache policy libc6
libc6:
Installed: 2.24-11+deb9u4
Candidate: 2.24-11+deb9u4
Version table:
*** 2.24-11+deb9u4 500
500 http://flightaware.com/mirror/raspbian/raspbian stretch/main armhf Packages
100 /var/lib/dpkg/status
**pi@piaware** : **~ $** apt search piaware
Sorting... Done
Full Text Search... Done
dump1090-fa/unknown 3.8.1 armhf [upgradable from: 3.7.1]
ADS-B Ground Station System for RTL-SDR
piaware/unknown 3.8.1 armhf [upgradable from: 3.7.1]
Open Aviation Data Exchange Protocol for ADS-B FlightFeeders
piaware-dbgsym/unknown 3.8.1 armhf
debug symbols for piaware
piaware-release/unknown 3.8.1 all [residual-config]
Metapackage for PiAware sdcard releases.
piaware-repository/unknown,now 3.8.1 all [installed]
Installs the PiAware apt repository configuration.
piaware-repository-testing/unknown 3.8.1 all
PiAware apt repository configuration (testing environment)
piaware-support/unknown 3.8.1 all [upgradable from: 3.7.1]
Support package for PiAware sdcard images.
piaware-web/unknown,now 3.8.1 all [installed,auto-removable]
PiAware landing webpage
Is this a known issue? Its a base Pi Aware image with no other changes - given its 100% PiAware I would expect it not to have broken dependancies.
Did something get mangled in the package dependancies with the focus on buster and Pi4?
No I do not want to re-image the SD card thanks, before someone suggests I start again and have backup and migrate all the local stats in the local rrd.
You are attempting to install the Buster packages on a Stretch install. I’m not sure how you got it into that state if it started life as an unmodified Stretch piaware sdcard image; what exactly did you do to atempt the upgrade? Usually this problem means that you have installed the wrong piaware-repository package version that doesn’t match the distribution you’re using. The upgrade path for a stretch install would have continued to use the stretch repository package.
(you mention local stats, which are not present in the base piaware image, so I assume this is actually not just a piaware sdcard image with no other changes)
apt-cache policy piaware and apt-cache policy piaware-repository would be useful to see.
Hi Obj,
So what I found just after posting was the /etc/apt/sources.list included stretch (as expected) but there was no upgrade available because the dependancies were for later code as noted above.
Where is the piaware-repository for stretch (perhaps I overwrote something following the 1st post - which I did after there was no upgrade shown at all after apt update and apt upgrade (and apt full-upgrade).
If I remove the release.deb from the first post I can over-write with the correct one if it was obvious where to obtain it?
It does seem to see both release sources, which is strange…
pi@piaware:~ $ apt-cache policy piaware
piaware:
Installed: 3.7.1
Candidate: 3.8.1
Version table:
3.8.1 500
500 http://flightaware.com/adsb/piaware/files/packages buster/piaware armhf Packages
3.8.1~bpo9+1 500
500 http://flightaware.com/adsb/piaware/files/packages stretch/piaware armhf Packages
*** 3.7.1 100
100 /var/lib/dpkg/status
pi@piaware:~ $ apt-cache policy piaware-repository
piaware-repository:
Installed: 3.8.1
Candidate: 3.8.1
Version table:
*** 3.8.1 500
500 http://flightaware.com/adsb/piaware/files/packages buster/piaware armhf Packages
100 /var/lib/dpkg/status
3.8.1~bpo9+1 500
500 http://flightaware.com/adsb/piaware/files/packages stretch/piaware armhf Packages
As I understand it I should be seeing the boo package which is for stretch?
Gave up and just re-imaged the SD (painful, needs physical access to pi which is mounted next to the piaware antenna)
The sources file is in /etc/apt/sources.list.d/piaware-stretch.list, installed as part of the piaware-repository package.
You can get the correct piaware-repository package for stretch at step 2 here: PiAware - dump1090 ADS-B integration with FlightAware - FlightAware
(make sure to follow the instructions for Stretch!)
It looks like you installed the piaware-repository package for Buster. The 3.8.1 packages are all Buster packages. The ~bpo9 packages are for Stretch.
Yes I followed the instructions in the first post of this thread, which is linked from the main website - that’s where I went wrong it appears.
Nearly back up now with new image, then have to re-install the Pi in antenna location.
Crazy question, but worth asking.
Can microSD card of a booted RPi be re-imaged over network (without physically removing microSD card from RPI)?
Something similar to this?
Cloning Booted RPi’s microSD card on Windows PC through Network
Not if it’s using a filesystem on the the sdcard.
It should be possible to build something that booted from an initrd (so it’s operating off a purely in-memory filesystem) and reimaged the sdcard. Actually obtaining the image to write in that environment might be tricky.
(This is a problem I’d like to solve for FlightFeeders, but it’s very hairy to get right)
1 Like
What trick phone manufacturers use to reimage? I have re-imaged (factory reset) my phone like this:
They’ll have a preloaded image on ROM and a bootloader that’s set up for this type of thing. The Pi has neither.
Googled and found following pages.
A quick look gives the impression this can be used in re-imaging a booted Pi. Will have to study in detail to find out.