On Mon, Apr 19, 2021 at 05:40:09PM +0200, Christoph Berg wrote: > Re: Julian Andres Klode > > > 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. > > This *is* a problem for users of "buster" where the suite will be > changing from "stable" to "oldstable". (Yes, we do release buster > twice, once as stable and then as oldstable.) > > Unless the fix that has closed #931566 is also applied to the apt > version in buster, things will explode horribly. Oh I see. That's tricky. > > Changed-By: Julian Andres Klode <jak@debian.org> > Changes: > apt (2.1.10) unstable; urgency=medium > . > * Default Acquire::AllowReleaseInfoChange::Suite to "true" (Closes: #931566) > > Notably, that needs to happen well before the bullseye release or else > systems will not be able to "apt-get update" non-interactively to > actually see the updated package. > > > 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. > > Yes, this part of the change is the good one. Pinning suite for > "buster" users is not. > > > > 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. > > On 2020-08-10 you said: > > 17:04 <Myon> juliank: is #931566 going to be fixed in buster as well? > 17:04 -zwiebelbot- Debian#931566: Don't complain about suite changes (Acquire::AllowReleaseInfoChange::Suite should be "true") - https://bugs.debian.org/931566 > 17:04 <juliank> Myon: yes > 17:04 <Myon> cool > 17:04 <Myon> thanks I see. Nobody pinged me since then, but it is indeed fixed in the 1.8.5 stable update that at least one release team member was not exited about. https://salsa.debian.org/apt-team/apt/-/compare/1.8.2.2...1.8.5 So it's up to the release team if they want 1.8.5 or whether we'll have to cherry-pick a subset of it into a 1.8.2.3. I think my opinion on that is clear - I don't want to maintain a 1.8.2.z branch, it's more work compared to just following the normal stable apt updates, and there's a lot less testing going on. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en
Attachment:
signature.asc
Description: PGP signature