From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: [PATCH v6 00/13] Deb-src caching
Date: Wed, 25 Nov 2020 06:51:18 +0100 [thread overview]
Message-ID: <c1d8f6d4-7303-14f2-3d3b-507e359245e1@siemens.com> (raw)
In-Reply-To: <20201124194520.GR31950@yssyq.m.ilbers.de>
On 24.11.20 20:45, Baurzhan Ismagulov wrote:
> Hello Vijai Kumar,
>
> On Wed, Sep 30, 2020 at 11:32:46AM +0530, Vijai Kumar K wrote:
>> Changes in v6:
>> - Rebase against latest next
>> - Address review comments from Henning
>> Git Tree: https://github.com/vj-kumar/isar/tree/vijai/debsrc6.3
>
> The code looks good to me. There is a couple of small issues, I'll reply to the
> respective patches.
>
> How do I use this? I've bitbake mc:qemuamd64-buster:isar-image-base, see
> downloads/deb-src/debian-buster, which contains only hello. Is this intended?
I would expect that everything a build pulled from deb-src goes into the
cache. IIRC, only hello is rebuilt from sources in these runs.
I wonder, though, and that might be a topic for some user manual
extension, how this series can also be used to fetch all sources
corresponding to all deployed binaries (compliance use case). Or does
this require extra logic?
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-11-25 5:51 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 6:02 Vijai Kumar K
2020-09-30 6:02 ` [PATCH v6 01/13] rootfs: Make rootfs finalize a separate task Vijai Kumar K
2020-11-24 19:47 ` Baurzhan Ismagulov
2020-09-30 6:02 ` [PATCH v6 02/13] deb-dl-dir: Cache host distro debs separately Vijai Kumar K
2020-09-30 6:02 ` [PATCH v6 03/13] meta: cache deb srcs as part of postprocessing Vijai Kumar K
2020-09-30 6:06 ` [PATCH v6 04/13] deb-dl-dir: Make debsrc_download faster Vijai Kumar K
2020-09-30 6:06 ` [PATCH v6 05/13] deb-dl-dir: Download files only belonging to the current image Vijai Kumar K
2020-09-30 6:07 ` [PATCH v6 06/13] deb-dl-dir: Factor out the mounting part Vijai Kumar K
2020-09-30 6:07 ` [PATCH v6 07/13] deb-dl-dir: Fix skipping of removed files Vijai Kumar K
2020-09-30 6:07 ` [PATCH v6 08/13] repository: Add a sanity test to check missing sources Vijai Kumar K
2020-09-30 6:18 ` [PATCH v6 09/13] base-apt: Introduce BASE_REPO_FEATURES Vijai Kumar K
2020-09-30 6:18 ` [PATCH v6 10/13] repository: Fix failures due to missing section Vijai Kumar K
2020-09-30 6:18 ` [PATCH v6 11/13] scripts/ci_build.sh: Enable deb-src caching Vijai Kumar K
2020-09-30 6:18 ` [PATCH v6 12/13] rootfs: Fix possible overwrite of existing resolv.conf Vijai Kumar K
2020-09-30 6:21 ` [PATCH v6 13/13] rootfs: Handle failures when postprocess is rerun Vijai Kumar K
2020-11-24 19:49 ` [PATCH v6 03/13] meta: cache deb srcs as part of postprocessing Baurzhan Ismagulov
2020-11-26 10:52 ` vijaikumar....@gmail.com
2020-11-26 11:03 ` Baurzhan Ismagulov
2020-11-26 11:07 ` vijaikumar....@gmail.com
2020-11-23 15:08 ` [PATCH v6 00/13] Deb-src caching vijaikumar....@gmail.com
2020-11-23 15:38 ` Jan Kiszka
2020-11-23 15:47 ` vijaikumar....@gmail.com
2020-11-24 5:41 ` Jan Kiszka
2020-11-24 6:30 ` vijaikumar....@gmail.com
2020-11-24 19:45 ` Baurzhan Ismagulov
2020-11-25 5:51 ` Jan Kiszka [this message]
2020-11-25 6:04 ` vijaikumar....@gmail.com
2020-11-25 6:48 ` Jan Kiszka
2020-11-25 7:16 ` vijaikumar....@gmail.com
2020-11-26 10:21 ` Baurzhan Ismagulov
2020-11-26 10:43 ` vijaikumar....@gmail.com
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=c1d8f6d4-7303-14f2-3d3b-507e359245e1@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=isar-users@googlegroups.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