From: "srinuvasan.a via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, cedric.hombourger@siemens.com,
ubely@ilbers.de, benedikt.niedermayr@siemens.com,
Adithya.Balakumar@toshiba-tsip.com,
srinuvasan <srinuvasan.a@siemens.com>
Subject: [PATCH 0/1] Fix deb-src caching issue
Date: Mon, 10 Mar 2025 17:21:48 +0530 [thread overview]
Message-ID: <20250310115149.1977443-1-srinuvasan.a@siemens.com> (raw)
From: srinuvasan <srinuvasan.a@siemens.com>
Dear isar-user,
When we enabled the deb-src caching during base-apt creation, we noticed a few deb-src packages missing in the pool.
Missing deb-src packages categorized in the below stages:
1. bootstrap related deb-src packages
2. imager related deb-src packages
3. image rootfs related deb-src packages
This regression we found after mmdebstrap migration, this issue addressed in the
below patch series, for more details, please refer to [1].
but here we use the /var/log/dpkg.log file to ensure the parsing of deb (from /var/cache/apt/archive)
is installed or not.
By default, mmdebstrap deletes the /va/log/dpkg.log file and we enabled that option in [1], but
our images are becoming longer reproducible.
Meanwhile, Cedric proposed one change to remove excessive calls to dpkg-deb in debsrc_download,
refer [2].
Here he completely rid of the checking status in /var/log/dpkg.log file and introduced the ftp-aptarchive
to scan all the deb packages and download the src against them, i feel it is more robust and works for
all the stages.
With his patch i validated the deb-src caching, now we can able to download the src packages for bootstrap
and image related packages only missing part here is imager related packages, this one is addressed with a refactor
of my patch 2/3 in [1].
Validated for amd64 and armf, it seems deb-src caching working fine and able to see all the deb-src packages.
I hope the combination of Cedric changes [2] and mine is the better solution for this deb-src caching issue.
[1]: https://groups.google.com/g/isar-users/c/8QstIaudyts
[2]: https://groups.google.com/g/isar-users/c/OwrSBmCPe0Y
Note: [PATCH 1/1] image: move deb-src-caching functionality after image creation heavily depend on [2].
srinuvasan (1):
image: move deb-src-caching functionality after image creation
meta/classes/image.bbclass | 8 +++++++-
meta/classes/rootfs.bbclass | 3 ++-
2 files changed, 9 insertions(+), 2 deletions(-)
--
2.39.5
--
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/20250310115149.1977443-1-srinuvasan.a%40siemens.com.
next reply other threads:[~2025-03-10 11:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 11:51 srinuvasan.a via isar-users [this message]
2025-03-10 11:51 ` [PATCH 1/1] image: move deb-src-caching functionality after image creation srinuvasan.a via isar-users
2025-03-18 16:45 ` 'Arjunan, Srinu' via isar-users
2025-03-20 5:31 ` Uladzimir Bely
2025-03-20 7:18 ` 'Arjunan, Srinu' via isar-users
2025-03-20 8:27 ` 'cedric.hombourger@siemens.com' via isar-users
2025-03-20 17:56 ` Uladzimir Bely
2025-03-20 18:02 ` 'cedric.hombourger@siemens.com' via isar-users
2025-03-21 5:32 ` Uladzimir Bely
2025-03-21 6:27 ` Uladzimir Bely
2025-03-21 6:32 ` 'cedric.hombourger@siemens.com' via isar-users
2025-03-21 7:06 ` Uladzimir Bely
2025-03-21 8:39 ` Uladzimir Bely
2025-03-21 13:50 ` 'cedric.hombourger@siemens.com' via isar-users
2025-03-27 16:55 ` Srinuvasan Arjunan
2025-04-03 12:58 ` [PATCH 1/2] meta/classes/rootfs: carry bootstrap list file until the image rootfs srinuvasan.a via isar-users
2025-04-03 12:58 ` [PATCH 2/2] image: move deb-src-caching functionality after image creation srinuvasan.a 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=20250310115149.1977443-1-srinuvasan.a@siemens.com \
--to=isar-users@googlegroups.com \
--cc=Adithya.Balakumar@toshiba-tsip.com \
--cc=benedikt.niedermayr@siemens.com \
--cc=cedric.hombourger@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=srinuvasan.a@siemens.com \
--cc=ubely@ilbers.de \
/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