On Sun, Apr 18, 2021 at 10:20:19PM +0200, Paul Gevers wrote: > Hi Julian, David, SRM, > > On Mon, 8 Jul 2019 09:11:48 +0200 Christoph Berg <myon@debian.org> wrote: > > Fwiw, I think this needs fixing in buster, not just in unstable. > > We're getting close to the release of bullseye and it has been brought > to my attention that this bug is still unfixed in buster. Once we > release bullseye, this bug is going to run havoc for our buster users. That's not accurate. This is _only_ a problem for users of testing, where the codename changes from time to time. For stable users, this is not a problem at all, more the opposite. Those poor souls who have stable in their sources.list won't suddenly get upgraded to bullseye. > > Can we somehow come up with a plan on how to handle this? Can we have a > fix in the next point release? Are there faster options than just > waiting some time after the next point release before we can release > bullseye, e.g. could the SRM allow an update to stable for the change of > an apt default to have the change earlier than the next point release? I have no intention of issuing a stable update. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Attachment:
signature.asc
Description: PGP signature