Upgrade von Buster auf Bullseye

[mschulze]

Hallo,

wir planen in den nächsten Monaten alle unsere Geräte (RevPi Core 3+ / S /SE) von Buster auf Bullseye zu aktualisieren.
Wir führen gerade Tests hierfür mit einem RevPi Core S durch und der Upgrade-Vorgang endet immer mit einem Fehler.

Ablauf:

• Gerät: RevPi Core S 8 GB

• Image: 2023-01-12-revpi-buster.img

• Vollständig aktualisiert: sudo apt update + sudo apt full-upgrade

• Paket-Repositiories von Buster auf Bullseye geändert

• Paket-Repositiories aktualisiert: sudo apt update

• Full-Upgrade schlägt fehl: Fehlende Abhängigkeiten für libc6-dev

• Gemäß Release Notes soll libgcc-8-dev installiert werden, welches jedoch ebenfalls aufgrund fehlender Abhängigkeiten fehlschlägt
  download/file.php?mode=view&id=2182

• Daraufhin wurde gcc-8-base installiert

• Nun kann das Full-Upgrade von Buster auf Bullseye gestartet werden

• Nach einigen Minuten bricht der Upgrade-Vorgang mit folgendem Fehler ab:
  download/file.php?mode=view&id=2183

Der konkrete Fehler lautet:

Code: Select all

Errors were encountered while processing:
 /tmp/apt-dpkg-install-1so5G7/17-revpi-tools_3.3.2-1+revpi11+1_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Hat sonst noch jemand dieses Problem?
Gibt es hierfür eine Lösung?

Vielen Dank im Voraus!
Michael Schulze

[u.biakoup]

Dear Community,

We'd like to bring an important point to your attention regarding upgrading from Buster to Bullseye. As of now, we do not provide official support for this upgrade process. There are several critical steps involved, and if not executed correctly, it can lead to issues such as network interfaces being renamed, which can result in network connectivity problems.

It's worth noting that even Raspberry Pi does not offer official supported upgrades from Buster to Bullseye, and attempting such an upgrade could potentially break your system. While there's a plan to share a script for this process within the community through our forum, it's important to understand that this would be at the community level and not officially supported.

In summary, we strongly advise against attempting a Buster to Bullseyeupgrade at this time. If you have any questions or concerns, please feel free to reach out to the community for assistance.

Best Regards

Ulrich Kouatang Biakoup | Technical Support

[mschulze]

So the only supported way to get to Bullseye would currently be to start from scratch by flashing (the most recent) image of Bullseye. Correct?

It would have been nice if the release notes have stated that the in-place upgrade from Buster to Bullseye is considered to be experimental / not-supported.

I see nothing like that in the document "Release_Notes_Bullseye_06_2023_EN.pdf":
download/file.php?mode=view&id=2185

Regards
Michael

[nicolaiB]

The problem is that with Bullseye the tool revpi-config was moved from webstatus to revpi-tools. During your upgrade the revpi-tools package is installed first and fails as it cannot override /usr/bin/revpi-config (see error message). A workaround could be to upgrade webstatus beforehand (or temporary uninstalled it during upgrade).

Nicolai

[mschulze]

Thanks Nicolai for the feedback!

But in the current state this is not usable for me.
We have a lot of devices abroad and I would need a robust and supported way of performing the Bullseye upgrade because there is no easy way to access the device if it doesn't come up after the upgrade.

So for me we are stuck on Buster for now.

Michael

[nicolaiB]

Did you try the above mentioned? This should allow an in place upgrade.

Nicolai

[mschulze]

Sadly as off today I don't have the device anymore in office. It's already shipped abroad with a fresh image of Bullseye.

Could you please give me a short list of commands how this would work out.
So I could test it on the next device.

Many thanks in advance!

[nicolaiB]

Something like this (total upgrade proces):

Code: Select all

# update Buster to latest patch leven
sudo apt update
sudo apt upgrade

# update repositories (buster -> bullseye)
sudo sed -i -e 's/buster/bullseye/g' /etc/apt/sources.list
sudo sed -ie 's/buster/bullseye/g' /etc/apt/sources.list.d/{raspi,revpi}.list

# fetch package list from updated repositories
sudo apt update

# install dependencies
sudo apt install libgcc-8-dev gcc-8-base

# remove webstatus due to conflicts (will be reinstalled later)
sudo apt remove revpi-webstatus

# perform upgrade stage 1
sudo apt upgrade

# reinstall webstatus
sudo apt install revpi-webstatus revpi-webstatus-redirect pictory

# perform upgrade stage 2
sudo apt full-upgrade

# Enable network manager instead of dhcpcd
curl https://gist.githubusercontent.com/nbuchwitz/06876674ebd0b2bab429f1a8506271a1/raw/303d71dab0b839a7057def34b71d7183d6b2e135/migrate-to-nm.sh -o /tmp/migrate-to-nm.sh
cat
bash /tmp/migrate-to-nm.sh

# ensure that local network configuration is migrated, if something else than dhcp is used !

# reboot RevPi
sudo reboot

[mschulze]

That looks very good. Thanks for that!

The only thing I would add is the replacement from Buster to Bullseye in the Node-RED package repository:

Code: Select all

sudo sed -ie 's/buster/bullseye/g' /etc/apt/sources.list.d/{raspi,revpi,nodesource}.list

As soon I have another RevPi on my desk I will test this procedure and give feedback.

Michael