3 ms·
Also security updates? Wouldn't that make the new version insecure at launch until someone pushes a thousand security updates at once (making it kind of 'testin
by lucb1e 7y ago
Also security updates? Wouldn't that make the new version insecure at launch until someone pushes a thousand security updates at once (making it kind of 'testing' again because none of these were in testing before and thus haven't been widely tested)?
You raise a good point since I notice I don't know the process as well as I thought I did, but it seems odd that the frozen testing repo would only get all security updates all at once months later.
- ufo 7y agoIIRC, Debian testing doesn't have a separate channel for security updates. Security updates are handled like regular updates: they start on Debian unstable and then flow down to Debian testing. The Debian wiki mentions that delays can be specially large after a new release comes out. I don't know if I was misremembering it or if it can be problematic both before and after a stable release comes out. Hopefully someone with more Debian experience can clear this up. https://www.debian.org/security/faq#testing https://www.debian.org/security/faq#testing
- ohazi 7y agoThis certainly used to be the case. There appears to be an actual channel now, though: http://security.debian.org/debian-security/dists/testing-security/ http://security.debian.org/debian-security/dists/testing-sec... I don't know if anything actually shows up here, but you no longer get the error for security.debian.org when you try to upgrade via s/stable/testing/ in sources.list.