Automatic updates not available for OS raspbian:10 (Raspbian GNU/Linux 10 (buster))
[2019-09-13 19:16 EDT] 309901 msgs recv'd from dump1090-mutabi (927 in last 5m); 309901 msgs sent to FlightAware
[2019-09-13 19:17 EDT] manual update (user-initiated via their flightaware control page) requested by adept server
[2019-09-13 19:17 EDT] performing manual update, action: piaware
[2019-09-13 19:17 EDT] child process 6221 exited with status EXIT 1
[2019-09-13 19:17 EDT] run-apt-get(6221): Automatic updates not available for OS raspbian:10 (Raspbian GNU/Linux 10 (buster))
[2019-09-13 19:17 EDT] skipping action piaware
[2019-09-13 19:17 EDT] update request complete
[2019-09-13 19:21 EDT] 310767 msgs recv'd from dump1090-mutabi (866 in last 5m); 310767 msgs sent to FlightAware
You have the testing repository package installed. You shouldn’t have this package installed and all bets are off; you’re picking up in-progress work that has not completed testing. Please remove and reinstall all piaware-related packages. If you are using the piaware sdcard image, please reimage with the 3.7.1 image.
If you’re already on the sdcard image, then reimaging is the simplest approach. If you’re not on a sdcard image then I leave it up to you to work out the best way to remove everything 3.7.2 related; I don’t know what’s installed.
While I’d prefer to continue to keep PiAware development open, this sort of problem means that we may have to restrict access to in-progress work.
I’ve globally disabled access to the testing repository URLs for now (which also blocks our own testing) to avoid any other accidental upgrades until I can work out what’s happening. (edit: FWIW, there are exactly 4 feeders currently claiming to be on 3.7.2 … and 3 of them are our test installs)
@waltkev, what is the history of this install and have you made any manual changes?
You’re just confusing people. Please don’t make me have to move future in-progress development work to our internal github.
In particular - we have to tag releases before they are ready for full release so that we can test them correctly. The assumption here is that people are not going to mess around with trying to build it from that tag before the release happens. If we can’t assume that, then the only real way to avoid multiple different versions of a release floating around - which is a maintenance nightmare - is to move all the development and testing off the public internet and only push the final version once it’s entirely done.
(Given that the tag is out there, I realise the assumption is already not a safe one - but it doesn’t really matter so long as whoever pokes at it knows what they’re doing. Posting random “hey here’s how you check out the 3.7.2 tag that probably isn’t going to be the final tag” makes things worse)
and the 3.7.2 package came through… I was not ready for the upgrade. It messed up my Skyview, and @wiedehopf graciously helped me restore my map. I later ran the “built-in” FlightAware device command: “Upgrade and restart dump1090” and the above log entries indicated that 3.7.2 had already been installed. The upgrade to 3.7.2. was not normal as it indicated things about “dump978-fa” which I had never seen before.