On Wed, Jan 24, 2018 at 02:10:43PM +1100, Trent W. Buck wrote: > As part of my Best Current Practice I set Default-Release "stretch", > to prevent accidental dist-upgrades when sources.list is in an unusual state. > (For THIS server, that's unlikely, but it's BCP so I do it everywhere.)
As your entire story depends on this, could you tell us please what you mean here? "accidental dist-upgrade" and "unusual state" don't make a lot of sense to me. I /guess/ you are talking about an upgrade from stretch to buster at the time buster becomes stable – but that would only happen if you would use "stable" in your sources.list instead of "stretch" and is hence kinda the point of using "stable" there… Nuking /var/lib/apt/lists isn't the best practice either as some security features use the "old" data to put up constraints for the "new" data – including that a repository can't change its Codename from "buster" to "bullseye" without a user explicitly confirming this (even if "stable" is written in the sources.list – implemented in 1.5 which is why I talk about stable+1 and stable+2 at the time of writing). Best regards David Kalnischkies
signature.asc
Description: PGP signature
