The Raspberry OS / Raspbian has been updated. It is now based on Debian 11 “Bullseye”.
News:
Release Notes:
https://downloads.raspberrypi.org/raspios_full_armhf/release_notes.txt
2 Likes
2021-10-30-raspios-bullseye-armhf-lite.zip
2021-10-30-raspios-bullseye-armhf.zip
2021-10-30-raspios-bullseye-arm64-lite.zip
2021-10-30-raspios-bullseye-arm64.zip
Piaware, dump1090-fa, dump978-fa, & piaware-web, BUILT & INSTALLED FROM SOURCE CODE
(1) DUMP1090-FA
Install
sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/piaware-ubuntu20-amd64/master/install-dump1090-fa.sh)"
(2) PIAWARE
2.1 - Install
sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/piaware-ubuntu20-amd64/master/install-piaware.sh)"
2.2 - configure
sudo piaware-config feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
sudo piaware-config allow-manual-updates yes
sudo piaware-config allow-auto-updates yes
sudo systemctl restart piaware
sudo systemctl restart dump1090-fa
(3) PIAWARE-WEB
Install
sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/piaware-ubuntu20-amd64/master/install-piaware-web.sh)"
(4) DUMP978-FA
4.1 - Install
sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/piaware-ubuntu20-amd64/master/install-dump978-fa.sh)"
4.2 - Serialize Dongles
sudo apt install rtl-sdr
rtl_eeprom -s 00001090 ##Plug-in 1090 dongle only
rtl_eeprom -s 00000978 ##Plug-in 978 dongle only
4.3 - Configure dump1090-fa and dump978-fa to use their respective dongles
sudo piaware-config uat-receiver-type sdr
sudo sed -i 's/^RECEIVER_SERIAL=.*/RECEIVER_SERIAL=00001090/' /etc/default/dump1090-fa
sudo sed -i 's/driver=rtlsdr[^ ]* /driver=rtlsdr,serial=00000978 /' /etc/default/dump978-fa
sudo reboot
2 Likes
Wonder what happens if you upgrade your existing installation to latest Raspberry OS based on Bullseye
Remarkable that you managed to sort that out.
I still have Buster running on my main PiAware but have a spare Zero running a portable unit. Installed Bullseye then ran you code. All working.
Geoff
1 Like
There’s not normally an official upgrade path but it can be fudged.
I won’t be fudging it 
2 Likes
Like this? Rated as “easy”
How to upgrade Debian 10 to Debian 11 Bullseye using the CLI - nixCraft (cyberciti.biz)
1 Like
Buster will be supported with upgrades for some time yet so no rush to upgrade anything but nice to know any re installations will be straight forward.
Geoff
Friend of mine still running Jessie - he is now going to upgrade, eventually
Geoff
I’m pretty sure that one or two of my Pis are on Jessie and some others still running Stretch. If they work, and they’re not external facing, I see no reason to change them.
2 Likes
I do have Debian 11 installed on my primary laptop.
But my local cloud device is still on Ubuntu Server 20.04 LTS, even if meanwhile 21.10 STS is out
If my primary laptop crashes - shit happens
If my cloud device crashes - my wife will deny serving food until it’s fixed
2 Likes
It’s not that it’s difficult to do, but that there can be unexpected consequences for doing so. It really depends on what packages you have installed and what changes have been made to the system configuration. In many cases upgrading will go smoothly, but there will always be a few circumstances where something unforeseen happens and things go a bit wrong.
Especially when the Pi is mounted 30ft up in the air 
1 Like
Posted one month ago (on Oct 8, 2021)
Upgraded Raspberry Pi OS Buster to Bullseye
It is a very lengthy upgrade process (took about 45 minutes)
1 Like
One thing to bear in mind, if you are using the old predictable interface names of ETH0 and WLAN0 they will not be available anymore in the bullseye release.
I have static IP’s for all devices and the upgraded pi appeared with a DHCP address.
So when you do an inplace upgrade and reboot at the end the PI will be online with a dhcp address and you have to change the interfacename to enxb… for an ethernetconnection and or wlx… for a wirelessconnection.
These can be adapted in the dhcpcd.conf file and this will reenable the static IP adressing again
1 Like
Aye, a friend had exactly this when he updated his Pihole last week, I noticed the interface name had changed when he sent me a screenshot of his ifconfig display.
Seems like a somewhat bonkers change.
the old names were supported until Buster but already abandonned since Jessie.
Knowing this can save so considerable time troubleshooting 
There is a good reason behind it, but it’s not necessarily relevant for a simple installation such as a raspberry pi. The intention is to make network names predictable - as in they are consistent for each interface between boots. Previously there were circumstances which could result in a names moving around various physical interface which could be problematic where a system is connected to more than one network.
There is a page on the Debian wiki talking about it: NetworkInterfaceNames - Debian Wiki
come on, that keeps you fit
That can be also the case with intermittent releases. However always a good option to get a fresh install removing all the shit installed over the years
2021-10-30-raspios-bullseye-armhf-lite.zip
After writing above image to microSD card, and successfully building & installing piaware, dump1090-fa, dump978-fa, and piaware-web packages on it, I successfully installed following also:
- Graphs by @wiedehopf
- Flightradar24 feeder (fr24feed)
- Planefinder feeder (pfclient)
- Radarbox24 feeder (rbfeeder)
- Adsbexchange feeder
- OpenSky feeder
4 Likes