I thought enough time had passed for all the "bugs" to be worked out of this "in-place upgrade" procedure. And so I gave it a go, starting with an RPi-5 (Lite, bookworm) that's not been used much. The upgrade seemed to go OK - the upgrade procedure completed successfully, and I've been just "kicking the tires" for a day or two with no issues noticed.
Here's the command I used:I tried upgrading a RPi Zero 2W (Lite, bookworm) using the same command, but had a completely different experience! I'm still struggling to complete the upgrade after 3 tries. The "hangup" here seems to be with the 'networking.service'. Please note that both of these bookworm systems used the networking.service - not NetworkManager.service.
I had expected that the network config might be an issue during the upgrade as I read that ifupdown no longer ships in the trixie distro. However, for the RPI 5, this was not an issue at all. As I said above, my Pi 5 system survived the trixie upgrade, and is still using 'networking. service' as a trixie system; it "just worked", and no manual adjustments were necessary.
During the Zero 2W upgrade, the 'apt' command went into a prolonged pause near the end while (apparently) trying to set up NetworkManager. It never actually completed. I know this isn't much to go on, but I'm posting here in the hope that someone has more background on this than I do, and can offer some suggestions. I've read through this entire forum topic/thread now, and noted that there was a revision to the "in-place upgrade" command... but before trying that I wanted to get some feedback here if possible.
Thanks for your time.
Here's the command I used:
Code:
sudo apt full-upgrade -y -o Dpkg::Options::="-force-confdef" -o Dpkg::Options::="-force-confnew" --purge -auto-removeI had expected that the network config might be an issue during the upgrade as I read that ifupdown no longer ships in the trixie distro. However, for the RPI 5, this was not an issue at all. As I said above, my Pi 5 system survived the trixie upgrade, and is still using 'networking. service' as a trixie system; it "just worked", and no manual adjustments were necessary.
During the Zero 2W upgrade, the 'apt' command went into a prolonged pause near the end while (apparently) trying to set up NetworkManager. It never actually completed. I know this isn't much to go on, but I'm posting here in the hope that someone has more background on this than I do, and can offer some suggestions. I've read through this entire forum topic/thread now, and noted that there was a revision to the "in-place upgrade" command... but before trying that I wanted to get some feedback here if possible.
Thanks for your time.
Statistics: Posted by shawn-o — Wed Oct 29, 2025 7:10 pm