Multiple sources lists in images

20 views
Skip to first unread message

Jan Kiszka

unread,
Feb 10, 2025, 3:41:01 AM2/10/25
to isar-users
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

Jan Kiszka

unread,
Feb 10, 2025, 3:56:43 AM2/10/25
to isar-users, Srinuvasan A
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.

Srinuvasan Arjunan

unread,
Feb 10, 2025, 4:11:57 AM2/10/25
to isar-users
  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.

Thanks,

Srinu

Jan Kiszka

unread,
Feb 10, 2025, 4:40:16 AM2/10/25
to Srinuvasan Arjunan, isar-users
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
Reply all
Reply to author
Forward
0 new messages