Hi Kurt, On Fri, 22 Sep 2017, Kurt Roeckx wrote: > I have to admit that I didn't consider derivatives that take a > snapshot of testing, and we also seem to have a large amount of > people that do use testing. My intention was to target the more > advanced users, and having it in testing might be affecting more > people than I thought. > > So I am considering to only disable it in unstable and not in > testing.
Thank you! > I'm actually surprised how few things broke. When an app outside of Debian breaks when trying to connect to a service running on a Debian machine, it's unlikely that said users will report it back to Debian... it's a long chain. Also servers will run stable and the large impact will only be noticeable once this reaches stable. On Fri, 22 Sep 2017, Kurt Roeckx wrote: > On Mon, Sep 11, 2017 at 11:33:22AM +0200, Raphaël Hertzog wrote: > > Or at least I would like a system-wide flag (in a configuration file?) to > > let me re-enable old protocols easily. > > It was my understanding that other people also prefered to do this > on a per package level and not system wide. I don't see why this would be mutually exclusive. We should be able to control the system-wide default and override the values for specific services too. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/