-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All about Bookworm #104
Comments
I had been running an install of piaware on a PiZeroW running raspian Bookworm and updating it regularly with the command:
Because I wanted to standardize all my systems to running 64bit I recently swapped out the hardware with a Zero2. I still use the same update sequence periodically. I now have several PiZero devices sitting idle and unused.
|
I installed PiAware on my Raspberry Pi OS Lite (64 Bit) image that I'd built using the Raspberry Pi Imager. I used the following command at the ssh prompt:
and then copied my old configuration from the previous SD card. |
Thanks @wcbonner and @eric1tran for the comprehensive info - the FlightAware website still points to Raspbian 8.2. This is just what I needed! |
Hi all,
I'd like to start here a consolidated discussion about piaware's compatibility with Raspian Bookworm, which was released in October 2023. I've been cruising on Bullseye for some time, and "apt-get full-upgrade" results in a bunch of zeroes.
I'm currently deployed over on the right-hand side of the Atlantic (one receiver, in my residence here) though I manage two receivers back in the US at close friends' in two locations in the mid-Atlantic area. It so happens I'll be taking some time off to reconnect with them all during this holiday season - maybe my last opportunity to do so for a year or or more - so I'm interested in getting a long-term roadmap about where this project is (or is not) going with Bookworm.
My hardware are Pi Zeroes running an oleo of "PiAware (SD Card) 9.0.1" and "PiAware (Debian Package Add-on) 9.0.1". What's the best long-term solution here?
The text was updated successfully, but these errors were encountered: