From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Srinuvasan Arjunan <srinuvasanasv@gmail.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: Multiple sources lists in images
Date: Mon, 10 Feb 2025 10:40:10 +0100 [thread overview]
Message-ID: <66e67acd-319d-447e-928b-6c5a800c2ecc@siemens.com> (raw)
In-Reply-To: <90c7feb4-45ad-401c-baa3-a04e15006d21n@googlegroups.com>
On 10.02.25 10:11, Srinuvasan Arjunan wrote:
>
>
> On Monday, February 10, 2025 at 2:26:43 PM UTC+5:30 Jan Kiszka wrote:
>
> On 10.02.25 09:40, 'Jan Kiszka' via isar-users wrote:
> > 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
> >
>
> Fun fact: It took the fix of f873658c981a to surface this. Was just
> wondering why isar-cip-core does not see this yet. It is on a slightly
> older revision due to various isar regressions.
>
> Jan
>
>
> Hi Jan,
>
> This issue was observed in cip-core few months ago, and moreover we
> are observing this issue with the mmdebstrap, not isar-bootstrap, I'm
> not sure about the history of moving /etc/apt/sources-list as
> bootstrap.list, might be for keeping any custom list.
>
Moving the file is really a debstrap thing. I guess we simply make it
also depend on sources.list.d being empty and can then eventually phase
it out. And the purging in case of non-empty IMAGE_LISTS needs to work
against the folder, not that legacy file.
I'll write some patch.
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/66e67acd-319d-447e-928b-6c5a800c2ecc%40siemens.com.
prev parent reply other threads:[~2025-02-10 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 8:40 'Jan Kiszka' via isar-users
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 [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=66e67acd-319d-447e-928b-6c5a800c2ecc@siemens.com \
--to=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=srinuvasanasv@gmail.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