From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: Question related to Sbuild CLEAN_SOURCE
Date: Thu, 10 Feb 2022 13:00:40 +0100 [thread overview]
Message-ID: <YgT+aCMu0+zPiNAn@ilbers.de> (raw)
In-Reply-To: <7d4a7da5-7ee5-51b3-0031-a407f72a5d72@siemens.com>
On Thu, Feb 10, 2022 at 12:27:44PM +0100, Jan Kiszka wrote:
> > I'm not sure what you mean with "sbuild convenience feature mode", could you
> > elaborate a bit?
>
> Read the reply of Josch that Quirin got.
Thanks, I had overlooked that specific wording there.
> OK, then we should switch to that and test it. I'd like to see the full
> picture, also in context of more layers. It was very helpful, also for
> the design discussions, that you converted 2 (besides Isar itself), but
> the problem showed up right with the 3rd one.
We had workarounded this issue also for the Isar kernel (KDIR not set during
cleaning). As cleaning is not necessary when passing a dsc, we can eliminate
the issue as a class and also avoid potential build interference through
garbage in the source directory (assuming the source package is done correctly)
by passing the dsc to sbuild -- currently evaluating.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2022-02-10 12:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b5ef299-ec8d-c180-c2b6-505294f5484b@siemens.com>
[not found] ` <164435326066.1656.13805705968480410488@localhost>
2022-02-09 10:36 ` quirin.gylstorff
2022-02-09 11:52 ` Baurzhan Ismagulov
2022-02-09 15:14 ` quirin.gylstorff
2022-02-09 15:37 ` Jan Kiszka
2022-02-10 9:59 ` Baurzhan Ismagulov
2022-02-10 11:27 ` Jan Kiszka
2022-02-10 12:00 ` Baurzhan Ismagulov [this message]
2022-02-10 8:47 ` Uladzimir Bely
2022-02-10 9:10 ` quirin.gylstorff
2022-02-11 10:54 ` Uladzimir Bely
2022-02-11 11:20 ` Jan Kiszka
2022-02-14 8:54 ` quirin.gylstorff
2022-02-14 9:47 ` Uladzimir Bely
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=YgT+aCMu0+zPiNAn@ilbers.de \
--to=ibr@radix50.net \
--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