From: Zhihang Wei <wzh@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: Re: [PATCH] Pull bullseye from archive.d.o
Date: Wed, 9 Sep 2026 09:02:55 +0200 [thread overview]
Message-ID: <a36c45bd-3a5f-4d15-9231-f865e3ca798c@ilbers.de> (raw)
In-Reply-To: <e69370a5-ef87-4c97-ac42-970a74e1cefa@siemens.com>
Applied to next, thanks.
raspios-bullseye-64.list needs the same change, I'll send a patch.
Zhihang
On 9/6/26 21:20, 'Jan Kiszka' via isar-users wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> LTS for Debian bullseye was closed by the end of August 2026. Pull it
> from the archive from now on. Security updates will not provided this
> way. Debian ELTS (https://www.freexian.com/lts/extended/) can provide
> longer support (package feed is subscriber-only).
>
> At this stage, debian-security was not archived. If this is restored at
> some point, we can also enable the related feed. For now, even more
> security updates will be missing in a rebuild.
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> meta/conf/distro/debian-bullseye.list | 13 +++++++------
> 1 file changed, 7 insertions(+), 6 deletions(-)
>
> diff --git a/meta/conf/distro/debian-bullseye.list b/meta/conf/distro/debian-bullseye.list
> index db1d98f1..7f1afd47 100644
> --- a/meta/conf/distro/debian-bullseye.list
> +++ b/meta/conf/distro/debian-bullseye.list
> @@ -1,8 +1,9 @@
> -deb http://deb.debian.org/debian bullseye main contrib non-free
> -deb-src http://deb.debian.org/debian bullseye main contrib non-free
> +deb http://archive.debian.org/debian bullseye main contrib non-free
> +deb-src http://archive.debian.org/debian bullseye main contrib non-free
>
> -deb http://deb.debian.org/debian-security bullseye-security main contrib non-free
> -deb-src http://deb.debian.org/debian-security bullseye-security main contrib non-free
> +# bullseye security archive is missing so far
> +#deb http://archive.debian.org/debian-security bullseye/updates main contrib non-free
> +#deb-src http://archive.debian.org/debian-security bullseye/updates main contrib non-free
>
> -deb http://deb.debian.org/debian bullseye-updates main contrib non-free
> -deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free
> +deb http://archive.debian.org/debian bullseye-updates main contrib non-free
> +deb-src http://archive.debian.org/debian bullseye-updates main contrib non-free
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/a36c45bd-3a5f-4d15-9231-f865e3ca798c%40ilbers.de.
prev parent reply other threads:[~2026-09-09 7:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 19:20 'Jan Kiszka' via isar-users
2026-09-09 6:19 ` 'MOESSBAUER, Felix' via isar-users
2026-09-09 6:23 ` 'Jan Kiszka' via isar-users
2026-09-09 7:02 ` Zhihang Wei [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a36c45bd-3a5f-4d15-9231-f865e3ca798c@ilbers.de \
--to=wzh@ilbers.de \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox