On Fri, Jun 20, 2025 at 10:15:21PM +0200, 🦓 wrote: > Gisteren schreef [email protected]: > > I can't tell you if it is the "best" way to do things, but I have always > > just deleted the entries associated with the previous release when I > > upgraded distros. I never have noticed any disadvantages when doing that. > > if that is so safe, then i would just suggest a stable > file:/etc/apt/sources.list.d/stable.list simply specifying > deb http://deb.debian.org/ stable main > deb-src http://deb.debian.org/ stable main >
Hi, That's *precisely* why we suggested to people to use the codename as part of the sources.list files. Bearing in mind we expect to release Testing as Trixie/Debian 13 in a couple of months ... If you pin to a codename of "forky" (once trixie releases), you'll get unstable and testing relating to forky and to stable, oldstable, oldoldstable as the years go by after release of forky as Debian 14. If you pin to "stable" as trixie releases, that's fine. Once forky releases you have a sudden unexpected flag day as *everything* changes underneath you. Anyone currently running *stable* in their sources.list files for bookworm is going to have this problem when trixie releases in a couple of months. It is always an argument whether Debian actually has one stable release or multiple releases running concurrently - is "Debian" current stable or the whole thing? All best, as ever, Andy Cater ([email protected])
