Hi, On Mon, 2023-10-30 at 17:39 +0700, Max Nikulin wrote: > On 30/10/2023 10:28, Osamu Aoki wrote: > > On Thu, 2023-09-21 at 21:56 +0700, Max Nikulin wrote: > > > On 18/09/2023 20:12, Osamu Aoki wrote: > > > > > > > > APT::Default-Release "testing"; > > > > > > > > I think this don't drive people to set this to "stable" as much. > > > > > > From my point of view it is a bit better, but hardly noticeable. And it > > > is still misleading for Debian users since testing has security updates > > > as well, thus not so trivial regexp is preferred. apt.conf(5) has more > > > examples, but neither of them is close to what might be used in real life: > > > > Although, repository for testing security updates exists, it is hardly used > > in > > practice. > > I feel some kind of miscommunication here. I was trying to say that > > APT::Default-Release "stable"; > > prevents updates from stable-security (bookworm-security).
Yes, I know that is what you said. "APT::Default-Release "testing";" is my initial improvement suggestion with minimal change. > This > repository is rather important, it is configured by installer, it is > mentioned in various docs, e.g. > https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_debian_archive_basics That is this document (my debian-reference) before this fix. My comment was aimed at upstream APT manpage or elsewhere outside of my control where I can't control. > deb http://security.debian.org/debian-security bookworm-security main > non-free-firmware contrib non-free > > I would not call it "hardly used". I am talking about testing-security being hardly used. > I agree that testing-security > repository is currently empty, but I assume, it may not be so during > late freeze stages. Moreover, having example for "testing", users may > try to blindly apply it for "stable". Release team has been saying not to expect testing-security to be used (with developer resource limitation etc.) If you care such risk, please use stable platform. > > Updated text: > > > > The target release archive can be set by the command line option, e.g., > > "apt-get > > install -t testing some-package" > > Thank you for improving of the docs. I consider the issue as fixed. Good.
