I noticed the other day when installing updates via Apt in the terminal, I was notified that Debian Buster is now old-Stable. That is normal every time a new Stable release is released. Debian also made changes to the security repo that needed to be changed. It is the line that reads security (dot) debian (dot) org/ , that needed to be changed to /debian-security. Replace the (dot) for a . , since the forum software wants to make that a URL link. I found this when I updated my two Debian 10 (Buster) boxes. I compared the sources.list files.
After that, I was able to run sudo apt update a second time with no errors shown. However, I did notice that Netrunner’s /etc/apt/sources.list file used the release name of stable instead of the codename of buster in the repo directives.
I ran sudo apt upgrade and a thousand or so packages needed to be updated. Obviously, that is due to Debian moving Bullseye from “Testing” to “Stable”. I knew that if I proceeded that it was going to move me to Debian 11. Because this is how you upgrade to a new version. You just change your codename in the sources.list file and run apt dist-upgrade.
I did a clean install of Netrunner 20.01 on another laptop and the same thing happened. Once I ran apt update and apt upgrade. I needed to correct the security entry in the source.list file. Then after an apt update and apt upgrade, I was running Debian 11.
My question is, was this what the Netrunner Maintainers intended to happen? It was a successful upgrade, I rebooted and everything has been fine. I tried doing a sudo apt dist-upgrade and no new updates were found. I did read in older posts that moving to Debian 11 wasn’t support, though that was when Debian 11 was in ‘Testing’. Now that Debian 11 the new Stable, is moving to Debian 11 supported?