On Mon, Jul 08, 2019 at 11:54:01AM +0300, Andrei POPESCU wrote: > On Lu, 08 iul 19, 03:10:53, Dave Sherohman wrote: > > On Sun, Jul 07, 2019 at 03:22:40PM +0200, Salvatore Bonaccorso wrote: > > > That will be actually a permanent change, see > > > https://lists.debian.org/debian-security/2019/06/msg00015.html . The > > > intention was actually do to it already in earlier cycle, but was not > > > possible (cf. > > > https://lists.debian.org/debian-security/2015/12/msg00015.html). > > > > What was the intended method for people upgrading from pre-buster > > versions to find out about this change? Just wait for them to try to do > > an update, get an error message, and hope that they ask on the mailing > > list instead of just commenting out the security updates line? > > Testing users are supposed to be able to handle such breakage. > > When bullseye becomes stable this will most likely be documented in the > Release Notes.
Ah, ok, thanks. I guess I wasn't following the thread properly and I was thinking this change was happening in buster, not bullseye. My mistake; sorry about that. -- Dave Sherohman
