I completely agree. Halting the Valid-Until updates before debian-security had been properly transitioned does not seem reasonable, and it affects all users relying on these repositories. From: [email protected] Date: Wed, Sep 9, 2026, 05:25 Subject: [External] Re: bullseye-security Valid-Until expiry after Debian 11 LTS EOL To: "杜德利"<[email protected]>, "Sylvain Beucler"<[email protected]>, < [email protected]> Cc: "鲍海亭"<[email protected]>, "雷玉亚"<[email protected]>, "佘开锐"<[email protected]>, "张延枫"<[email protected]>
On Sep 8, 2026 22:14, Sylvain Beucler <[email protected]> wrote: > > Hi, > > On 07/09/2026 07:16, 杜德利 wrote: > > Dear Debian LTS Team, > > I would like to confirm whether the current bullseye-security repository > > state after Debian 11 LTS end-of-life is expected, and what the > > recommended handling is. > > Debian 11 bullseye LTS reached end-of-life on 31 August 2026. > > Environment: > > > > * Debian 11 (bullseye) > > * Mirror: http://mirrors.cloud.aliyuncs.com/debian-security > > mirrors.cloud.aliyuncs.com/debian-security> > > * Test method: set system date to 2026-09-09 and run apt-get update > > > > *Observed error:* > > ** > > As additional context, the security InRelease metadata we checked from > > the Debian side is already for Debian 11 / bullseye-security: > > We are also seeing that some packages are no longer available from the > > bullseye-security repository. > > We have seen that Debian 10 security content was eventually moved to > > archive infrastructure, so we would like to understand whether Debian 11 > > bullseye-security is expected to follow the same transition path, and if > > so, what repository configuration users should adopt. > > Could you please clarify: > > > > 1. whether the current behavior is the expected post-EOL state for > > bullseye-security; > > AFAICS security.debian.org is always signed with a short-term > Valid-Until, and regenerated often. When bullseye-lts got EOL this > stopped being updated, which seems consistent, if a little inconvenient, > resulting in your error. > > If you need to keep using bullseye-lts, you could: > > - use '-o Acquire::Check-Valid-Until=false' to bypass the error > > - switch to bullseye ELTS and keep getting security updates > https://www.freexian.com/lts/extended/ > > > 2. whether Debian 11 bullseye-security is expected to move to archive > > infrastructure, and what the recommended handling is for systems > > that still need final migration / verification work. > > From prior experience, moving to archive.debian.org can take months and > is not scheduled precisely, so you should have the time to finish > handling the final migrations. This is not handled by the Debian LTS > team so I can't help you more there. > > Cheers! > Sylvain Beucler > Debian LTS Team IMO, this shouldn't have happened before it was archived. There is something wrong in this process. Cheers, Thomas Goirand (zigo)
