From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Multiple sources lists in images
Date: Mon, 10 Feb 2025 09:40:56 +0100 [thread overview]
Message-ID: <9fd055d1-04de-4ec6-a246-ad2289aac19e@siemens.com> (raw)
Hi all,
seems the switch to mmdebstrap caused some more minor regression:
$ tar -tf build/tmp/deploy/bootstrap/debian-bookworm-amd64.tar.zst | \
grep /etc/apt/source
./etc/apt/sources-list
./etc/apt/sources.list.d/
./etc/apt/sources.list.d/0000bootstrap.list
Our image class later on makes sources-list to
sources.list.d/bootstrap.list, and now we have them twice. When calling
apt on the target, you will be flooded with warnings (things still work
at least).
Before simply deleting 0000bootstrap.list from the mmdebstrap output, I
would first of all like to reflect if what we are doing in image.bbclass
do_rootfs_finalize is still up-to-date with mmdebstrap. What was the
idea behind moving /etc/apt/sources-list around?
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
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/9fd055d1-04de-4ec6-a246-ad2289aac19e%40siemens.com.
next reply other threads:[~2025-02-10 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 8:40 'Jan Kiszka' via isar-users [this message]
2025-02-10 8:56 ` 'Jan Kiszka' via isar-users
2025-02-10 9:11 ` Srinuvasan Arjunan
2025-02-10 9:40 ` 'Jan Kiszka' via isar-users
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=9fd055d1-04de-4ec6-a246-ad2289aac19e@siemens.com \
--to=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