From: Jan Kiszka <jan.kiszka@siemens.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
isar-users@googlegroups.com
Subject: Re: [PATCH 1/1] sources.list: add non-free-firmware repository
Date: Thu, 2 Feb 2023 13:51:22 +0100 [thread overview]
Message-ID: <af8c0639-2c14-0f60-db12-7583c17f929d@siemens.com> (raw)
In-Reply-To: <20230202095115.1705169-1-felix.moessbauer@siemens.com>
On 02.02.23 10:51, Felix Moessbauer wrote:
> The Debian project has taken the decision in 2022-10 to
> create a new repository component non-free-firmware, and
> include its content on installation media for the upcoming
> Debian release bookworm. This has to be reflected in our
> sources.list from bookworm on.
>
> While the non-free-firmware repository contains only the
> firmware parts, we could remove non-free as the intention
> of adding non-free was just to get the non-free firmware
> packages. However, still many firmware packages are not in
> the correct repository, so better keep non-free for now.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> meta/conf/distro/debian-bookworm.list | 12 ++++++------
> meta/conf/distro/debian-sid.list | 4 ++--
> 2 files changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/meta/conf/distro/debian-bookworm.list b/meta/conf/distro/debian-bookworm.list
> index f47e46ef..cbc0ca3b 100644
> --- a/meta/conf/distro/debian-bookworm.list
> +++ b/meta/conf/distro/debian-bookworm.list
> @@ -1,8 +1,8 @@
> -deb http://deb.debian.org/debian bookworm main contrib non-free
> -deb-src http://deb.debian.org/debian bookworm main contrib non-free
> +deb http://deb.debian.org/debian bookworm main contrib non-free-firmware non-free
> +deb-src http://deb.debian.org/debian bookworm main contrib non-free-firmware non-free
>
> -deb http://deb.debian.org/debian-security/ bookworm-security main contrib non-free
> -deb-src http://deb.debian.org/debian-security/ bookworm-security main contrib non-free
> +deb http://deb.debian.org/debian-security/ bookworm-security main contrib non-free-firmware non-free
> +deb-src http://deb.debian.org/debian-security/ bookworm-security main contrib non-free-firmware non-free
>
> -deb http://deb.debian.org/debian bookworm-updates main contrib non-free
> -deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free
> +deb http://deb.debian.org/debian bookworm-updates main contrib non-free-firmware non-free
> +deb-src http://deb.debian.org/debian bookworm-updates main contrib non-free-firmware non-free
> diff --git a/meta/conf/distro/debian-sid.list b/meta/conf/distro/debian-sid.list
> index 2b8158cc..ccddf87d 100644
> --- a/meta/conf/distro/debian-sid.list
> +++ b/meta/conf/distro/debian-sid.list
> @@ -1,2 +1,2 @@
> -deb http://deb.debian.org/debian sid main contrib non-free
> -deb-src http://deb.debian.org/debian sid main contrib non-free
> +deb http://deb.debian.org/debian sid main contrib non-free-firmware non-free
> +deb-src http://deb.debian.org/debian sid main contrib non-free-firmware non-free
sid-ports is not affected by this, right?
Jan
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2023-02-02 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 9:51 Felix Moessbauer
2023-02-02 12:51 ` Jan Kiszka [this message]
2023-02-02 14:01 ` Moessbauer, Felix
2023-02-06 4:00 ` Uladzimir Bely
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=af8c0639-2c14-0f60-db12-7583c17f929d@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.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