Debian 11 "bullseye" released

Posted Aug 17, 2021 16:50 UTC (Tue) by docontra (guest, #153758)
In reply to: Debian 11 "bullseye" released by clump
Parent article: Debian 11 "bullseye" released

If sources.list is *unmodified from the installation* (using an official installer image), it should use release codenames (i.e., buster for Debian 10) for stable releases and late testing images instead of stable/testing. In that case, you wouldn't get that message. On the machines I manage that I've yet to migrate to Debian 11 I didn't get any notification, but I did get a similar notification stating that bullseye had become the stable release. Personally, I prefer to keep the distro codenames in sources.list instead of using stable to ensure the distro version upgrade is on my terms (regarding timing), but to each their own :)

PD: Note that the security repo has migrated on debian 11 from stable/updates to stable-security ; luckily for me, on all the machines I've upgraded so far that was the biggest hurdle.

Debian 11 "bullseye" released

Posted Aug 18, 2021 1:26 UTC (Wed) by pabs (subscriber, #43278) [Link]

Please note that if you have default-release or pinning setup, you will need to adjust your config to account for the new security suite name:

https://www.debian.org/releases/bullseye/amd64/release-no...

If your APT configuration also involves pinning or APT::Default-Release, it is likely to require adjustments as the codename of the security archive no longer matches that of the regular archive. An example of a working APT::Default-Release line for bullseye looks like:

APT::Default-Release "/^bullseye(|-security|-updates)$/";

which takes advantage of the undocumented feature of APT that it supports regular expressions (inside /).