Updating FA & dump1090-fa from 6.1->7.2?

Although the FA website doesn’t show any updates for my existing 6.1 version a quick sudo apt update / apt list --upgradable shows;

dump1090-fa/unknown 7.2~bpo10+1 armhf [upgradable from: 6.1]
piaware-repository/unknown 7.2~bpo10+1 all [upgradable from: 6.1]
piaware/unknown 7.2~bpo10+1 armhf [upgradable from: 6.1]

Along with a further 143 Raspbian Buster updates as I haven’t updated in a while!

Amongst those it also shows;

mlat-client/unknown 0.2.11 armhf [upgradable from: 0.2.11]

which I have on Hold to prevent a slightly buggy AirNav Systems from overwriting the bug-fixed version from abcd567

What I would like to know is it safe to just go ahead and issue sudo apt full-upgrade which will update the FA stuff along with dump1090-fa?

And can I finally take mlat-client off hold or have they still not fixed that annoying bug yet?

I always get nervous before updating my VR Pi as in addition to feeding FA it also feeds FR24, RB24 and ADSB-X and I am thinking about feeding Freedar - does anybody else here share data with Freedar as I done a search and nothing turned up…

Thanks & kind regards,
-=Glyn=-

@GlynH

If I was in your place, I will simply use a SPARE microSD card to write Raspberry Pi OS Bullseye, then install lateat versions of all feeders.

Still the bug persists. Please brows these two very recent threads in RadarBox24 forum. Problem was finally solved by purging RB24 supplied mlat-client and installing mlat-client built from source code. The mlat-client source-code is available at github/mutability. :slight_smile:

mlat error - July 15, 2022

MLAT not working after Raspi update and selecting yes instead of no for rbfeeder - July 16, 2022

 

Thanks for the reply abcd,

I have 5 Pi’s carrying out various tasks and I like to keep them all the same so not planning to update from Buster to Bullseye on just one of them at the moment.

Likewise not planning to update all 5 to Bullseye at the moment either! :crazy_face:

Are we saying that FA 7.2 is Bullseye only and will not run under Buster and if so does that mean that dump1090-fa v7.2 is also Bullseye specific?

If it is not recommended I update either while still running Buster do you think it would be OK to do what I currently do with mlat-client and put a sudo apt-mark hold on both piaware and dump1090 just so I can continue to update the rest of my system?

If so what filenames would I use to stop piaware being updated based upon the above apt list --upgradable as although it looks easy to add dump1090-fa I am confused as to what I should add for the remaining piaware-repository/unknown and piaware-unknown unless it is as simple as specifying piaware? :thinking:

I also notice rbfeeder has an update so fingers crossed that won’t upset anything;

rbfeeder/unknown 1:1.0.8+deb10 armhf [upgradable from: 0.4.3-20210909231001]

I do have a recent clone of my currently working system so can always revert to that in the event of a meltdown but I’m just trying to minimise the impact of updating in the first place.

I’ll retain the hold on mlat-client as I have no faith whatsoever in AirNav ever fixing that particular bug if waiting for them to fix the annoying bug of not being able to highlight aircraft in their v6.02.003 Windows app since they modified it to support their ludicrously overpriced XRange devices in 2017/2018 is anything to go by not to mention many more bugs some of which I was reporting back in 2008 :astonished:

I’m very happy with the performance of my VR Pi (apart from slipping just outside of the Top 10 UK RadarBox Ranking recently) but really should take on board some of the 143 Raspbian updates sat there waiting patiently to be installed…

Thanks & kind regards,
-=Glyn=-

If you recall it was you who recommended I use the hold on mlat-client some time ago and that has worked exactly as it should have done and prevented it getting overwritten by the buggy version.

No, ver 7.2 of piaware, dump1090-fa, & dump978-fa are available for BUSTER also, but package for Buster will have an additional suffix ~bpo10+1 in their name.

~bpo10 = back port debian version 10

To verify, run these commands:

sudo apt update  

apt-cache policy piaware   

apt-cache policy dump1090-fa

 

Please also see this page

 

image

Ah that would explain why I see ‘bpo10’ references when I run apt list --upgradable;

dump1090-fa/unknown 7.2~bpo10+1 armhf [upgradable from: 6.1]
piaware-repository/unknown 7.2~bpo10+1 all [upgradable from: 6.1]
piaware/unknown 7.2~bpo10+1 armhf [upgradable from: 6.1]

The commands you suggest I run return;;

apt-cache policy piaware
piaware:
Installed: 6.1
Candidate: 7.2~bpo10+1
Version table:
7.2~bpo10+1 500
500 http://flightaware.com/adsb/piaware/files/packages buster/piaware armhf Packages
*** 6.1 100
100 /var/lib/dpkg/status

apt-cache policy dump1090-fa
dump1090-fa:
Installed: 6.1
Candidate: 7.2~bpo10+1
Version table:
7.2~bpo10+1 500
500 http://flightaware.com/adsb/piaware/files/packages buster/piaware armhf Packages
*** 6.1 100
100 /var/lib/dpkg/status

Thanks for the link abcd…I’ve read that and other stuff but but as usual the more I read the more confused I get so do you think it would be OK to just run sudo apt full-upgrade and let it take care of itself along with the system updates or should I upgrade piaware by itself using the following;

wget https://flightaware.com/adsb/piaware/files/packages/pool/piaware/p/piaware-support/piaware-repository_7.2~bpo10+1_all.deb
sudo dpkg -i piaware-repository_7.2~bpo10+1_all.deb

If I have to install it by itself should I then also sudo apt-get install dump1090-fa afterwards?

They both show when I apt list --upgradable so hoping the usual sudo apt full-upgrade might work…

You know me abcd…I need it spelt out in plain English and some hand-holding before I commit even though I have a cloned micro SD Card waiting to go just in case and it usually seems to work anyway! :wink:

I’ve got to the age now that if something catastrophic happened and my cloned card also failed that would be the end of my feeding as I don’t think I could go through all of the install/configuration of the last two years again… :crazy_face:

I think running sudo apt full-upgrade will be a huge upgrade, as it will upgrade the OS from Buster to Bullseye.

Better try these simple commands which will upgrade only piaware and dump1090-fa from ver 6.1 to ver 7.2 (and may also upgrade few other packages as well which are dependencies for piaware and dump1090-fa)

sudo apt update  

sudo apt install piaware  

sudo apt install dump1090-fa    

 

Thanks again abcd…although I did update all five of my other Pi 4’s yesterday using sudo apt full-upgrade and they’re definitely still all on Raspbian GNU/Linux 10 (buster)? :thinking:

cat /etc/os-release
PRETTY_NAME=“Raspbian GNU/Linux 10 (buster)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“10”
VERSION=“10 (buster)”
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL=“http://www.raspbian.org/
SUPPORT_URL=“RaspbianForums - Raspbian
BUG_REPORT_URL=“RaspbianBugs - Raspbian

But you are probably right in that I should play it safe and do it in stages.

I’ll clone a second card just in case my first cloned card throws a hissy fit! :rofl:

Thanks & kind regards,
-=Glyn=-

No it won’t, unless you’ve also changed your apt sources list to the Bullseye repos.

You are right. It wont without adding Bullseye repo in apt sources list.

I did upgraded Buster to Bullseye by adding bullseye repo to buster, and even posted the method last year, but completely forgot it now. Seems aging is taking its toll.

Upgraded Raspberry Pi OS Buster to Bullseye

 

2 Likes

I’m right there with you on that. I spend some time nearly every day thinking about the hereafter. I walk across the room then stop and think, “What am I here after?”

2 Likes

Wait ‘til you get to be my age (pushin’ 80). Then you’ll need to think about how to get across the room before wondering why you want to go there…

1 Like

Well just to close the loop on this thread its taken me all this time to pluck up the courage to update my VR Pi and as before there was actually nothing to worry about when it came to it.

Not only did I clone the spare SD card I keep plugged in at all times but I also cloned a second one just in case such was my paranoia so if worst came to worst I could just slot in another SD card and of course if that one had an issue I had my second cloned SD card I could switch in! :stuck_out_tongue_winking_eye:

I ended up with 218 updates in all including two of the four VR packages; FA/dump1090 7.2 along with rbfeeder 1.0.8

A quick sudo apt update followed by sudo apt full-upgrade just went through the process of updating everything with only two prompts - one about whether to keep or replace /etc/lighttpd/conf-available/89-skyaware.conf and the other offering the same decision on whether to keep or replace /etc/rbfeeder.ini and I chose the default option on both which was to keep current version.

A quick sudo reboot and the Pi came straight back up with everything appearing to work perfectly as before!

So a quick thank you to those who gave me the confidence to forge ahead with the update. Cheers!

Gives me more confidence to update in the future but I won’t leave it so long next time.

I do wonder just what the differences were between the new and existing config files were though? There was an option to show the differences between the versions but I didn’t want to tax the installer so just accepted the defaults.

Does anybody know what those differences are and is there an easy way to compare the differences retrospectively?

Thanks & kind regards,
-=Glyn=-

So did you also update to Bullseye or you still on Buster ? just curious. :wink: