https://wiki.debian.org/StableUpdates
It does not state that it is required either, and the wording suggests it is an opt-in to enable. Look, I have been running for years servers by disabling stable-updates. Provided very rock solid stable predictable upgrades, every ~2 months the minor release upgrade, and continuous security updates. Please read all the text I wrote also, I tried to explain clearly, and maybe I should try to explain it again: If you do 13.6 exact release, does it means it should contain already packages that have been updated in stable-updates after the day of release? Because for cloud image this is what happened. And it can be tested. Start a fresh vm from 13.6 cloud image, disable updates, and all python dependent software fails to install. The way I understood for years Debian repos is: Stable - base, mandatory Security - critical, required 100% in under certification environments Updates - proposed updates, not security, that are nice to have, an opt-in if you accept possible every day updates available. Disabling stable-updates, makes upgrades on a system more predictable, easier to trust, and less verbose for environments where I have to create tickets with list of all packages that will be included. Is my logic wrong, to build a cloud image that if states 13.6, it will have packages 100% from 13.6 and ideally the last security updates that were until the process starts? > On 26 Aug 2026, at 15:50, Noah Meyerhans <[email protected]> wrote: > > stable-updates
