Old timer “dist-upgrade” and relatively new “full-upgrade” do the same thing, but “upgrade” does somewhat different thing.
I initially used only “upgrade”, and noticed warnings whenever tried later to update or install a new package.
I then again wrote the image to microSD card, and this time used “dist-upgrade”, and there were no warnings when subsequently tried to update or install a new package.
I then again wrote the image to microSD card and this time used “full-upgrade” and it behaved exactly same as “dist-upgrade” i.e. no problems when subsequently tried to update or install a new package.
I ran into a nice quirk that took me some time to figure out so let’s document it here
Bullsey has a new feature hidden in the graphical user interface called Connman ( Connection manager).
All my Raspberry Pi’s I’ve upgraded claimed a DHCP adress on the network and they also have a static IP adress.
I wanted to get rid of the DHCP addresses and couldn’t figure out how.
Dhcpcd.conf file was set correctly, i could release the address with the command sudo dhclient -v -r and within 24 hrs it was back again.
After a few days of trial and error I stumbled upon this post describing the feature:
Turns out that Connman is set to automatic by default by Bullseye and that way is claiming a DHCP address.
So if you have this issue then loging into the Pi then this might be the solution.
Either use the GUI interface by running raspi-config and let the system login to the desktop.
Under preferences you will find the Connman option.
Set the IPv4 adress from Automatic to Manual and set the Static IP address.
Then hit apply and your address wil be changed to the static IP adress.
When done rerun the raspi-config and revert back to the CLI if you are running your Pi from there.
After experimenting with successful upgrade to Bullseye in following ways, I came to conclusion that currently there is no real advantage of doing so (EXCEPT for Pi Zero 2 W which has some issues with Buster):
In-place upgrade of Piaware SD card image from Buster to Bullseye
In-place upgrade of Raspi OS Buster to Bullseye
Re-imaging with Raspi OS Bullseye, and package install by building packages from source code.
It is better to continue with “Piaware SD card image 6.1 (Buster based)”, OR “Raspi OS Buster” with package install, till Flightaware releases Bulseye based SD card image and packages for piaware & dump1090-fa.
One problem with trying to upgrade Buster to Bullseye while holding back current versions of PiAware 6.1’s dependencies is that you end up with a FrankenDebian that’s part Bullseye, part Buster and that can lead to issues later on (plus I suspect that FlightAware staff won’t support such a system.) See DontBreakDebian - Debian Wiki. Problems may not occur right away but start happening weeks or months later. Not good if your Pi’s in a remote or difficult to access location. You’re better off freshly installing Raspbian Bullseye from scratch then either compiling PiAware from source so it builds for the versions of system libraries etc. that come with Bullseye or even better, waiting for PiAware 7 packages to be available before installing Bullseye. Buster will be supported by Debian until June 2024 so there’s no reason to hurry and upgrade now. You have plenty of time.
