Le 27 octobre 2022 20:03:57 GMT+02:00, "Andrew M.A. Cater"
<amaca...@einval.com> a écrit :
>On Thu, Oct 27, 2022 at 09:05:54AM -0400, Greg Wooledge wrote:
>> On Thu, Oct 27, 2022 at 06:55:12AM -0600, Charles Curley wrote:
>> > On Thu, 27 Oct 2022 09:47:39 +0200
>> > Hogren <hog...@iiiha.com> wrote:
>> >
>> > > RUN echo 'deb http://deb.debian.org/debian testing main' >
>> > > /etc/apt/sources.list
>> >
>> > I haven't yet read the entire email, but this sticks out like a sore
>> > thumb. It is almost certainly not what you want. This completely
>> > obliterates your entire /etc/apt/sources.list, replacing it with a
>> > single line. For one thing, you lose any reference to the security repo.
>>
>> To be fair, there *isn't* a security repository for testing. Well,
>> technically there is one, but it hasn't been used in years. It's empty.
>> There's nothing in it.
>>
>
Thanks for your infos.
>There's another problem: if you pin to stable or testing, then you get an
>unpleasant shock when the next iteration of stable is released and there
>are suddenly hundreds of updates.
>
>The whole reason that codenames were brought into Debian was because someone
>released a version of Debian that was not yet ready as "Debian 1.0" on their
>CD set. Debian never released a 1.0 and instead went from 0.97 to 1.1.
>
>if you pin to a release name, then you don't have a flag day when everything
>changes.
>
>If you *really* want to pin to testing - with no security support - you
>can. The other option is to pin to bookworm which won't change when it
>becomes stable/oldstable or whatever. Otherwise, when bookworm gets
>released, testing magically becomes trixie.
>
>Hope this helps, as ever,
>
>Andy Cater
>
Yes Andy I know. In fact, I previously tested with releases names, and in one
of my several tests, I modified to stable/testing. I keep these in my
demonstration but the problem still here with the two options.
In all cases, thank you.
Anybody can say if this is a bug or not ?
Regards,
Hogren
