From: Henning Schild <henning.schild@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH] meta: Reenable deps checking
Date: Fri, 10 Dec 2021 08:03:44 +0100 [thread overview]
Message-ID: <20211210080344.44a2bb24@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20211210064001.30136-1-ubely@ilbers.de>
Am Fri, 10 Dec 2021 07:40:01 +0100
schrieb Uladzimir Bely <ubely@ilbers.de>:
> For a long time Isar uses '-d' option passed to dpkg-buildpackage.
> This makes it skip dpkg-checkbuilddeps stage.
>
> The option was added in
> https://github.com/ilbers/isar/commit/b18ad30c8c and now it seems not
Please use only the sha here, that will enable gitk an keep the
"remote" out of the history.
In fact you could think about using "git revert" ... will need conflict
resolution i guess.
Henning
> to be needed anymore.
>
> Removing the option makes build process more strict, but can cause
> build errors in downstream, if ':native' build-dep is used in a wrong
> way.
>
> Related discussion is here:
> https://lists.debian.org/debian-devel/2021/12/msg00135.html
>
> Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
> ---
> meta/recipes-devtools/buildchroot/files/build.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/buildchroot/files/build.sh
> b/meta/recipes-devtools/buildchroot/files/build.sh index
> 8e6507c6..b2e60252 100644 ---
> a/meta/recipes-devtools/buildchroot/files/build.sh +++
> b/meta/recipes-devtools/buildchroot/files/build.sh @@ -19,4 +19,4 @@
> if [ "$use_ccache" == "1" ]; then export PATH=/usr/lib/ccache:$PATH
> fi
>
> -${GBP_PREFIX}dpkg-buildpackage -a$target_arch -d --source-option=-I
> +${GBP_PREFIX}dpkg-buildpackage -a$target_arch --source-option=-I
prev parent reply other threads:[~2021-12-10 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 6:40 Uladzimir Bely
2021-12-10 7:03 ` Henning Schild [this message]
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=20211210080344.44a2bb24@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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