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
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.
Thanks,
Srinu
--
Siemens AG, Foundational Technologies
Linux Expert Center