From: Henning Schild <henning.schild@siemens.com>
To: <isar-users@googlegroups.com>
Cc: "Kiszka, Jan (CT RDA IOT SES-DE)" <jan.kiszka@siemens.com>
Subject: Re: [PATCH 1/2] meta: remove dead code from buildchroot script
Date: Tue, 5 May 2020 13:02:34 +0200 [thread overview]
Message-ID: <20200505130234.0af1fc06@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20200505110026.6390-1-henning.schild@siemens.com>
The first one is a cleanup. And the second one can hopefully help find
out why bullseye currently does not build anymore.
https://github.com/henning-schild-work/isar/tree/henning/staging3
Henning
Am Tue, 5 May 2020 13:00:25 +0200
schrieb Henning Schild <henning.schild@siemens.com>:
> From: Henning Schild <henning.schild@siemens.com>
>
> 6d0ce719f2a1e8bd01bc4ed3005bb16058a0a9ff dropped code that used the
> variable
>
> We do not need it anymore so remove it.
>
> Signed-off-by: Henning Schild <henning.schild@siemens.com>
> ---
> meta/recipes-devtools/buildchroot/files/common.sh | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/buildchroot/files/common.sh
> b/meta/recipes-devtools/buildchroot/files/common.sh index
> f75a84e4bf..0063a38e61 100644 ---
> a/meta/recipes-devtools/buildchroot/files/common.sh +++
> b/meta/recipes-devtools/buildchroot/files/common.sh @@ -18,7 +18,6 @@
> fi # Create human-readable names
> target_arch=$2
>
> -debian_version=$(cut -c1 /etc/debian_version)
> set_arch="--host-arch $target_arch"
>
> # Go to build directory
next prev parent reply other threads:[~2020-05-05 11:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 11:00 Henning Schild
2020-05-05 11:00 ` [PATCH 2/2] meta: make builddep installation verbose Henning Schild
2020-05-05 11:02 ` Henning Schild [this message]
2020-05-06 8:57 ` [PATCH 1/2] meta: remove dead code from buildchroot script Baurzhan Ismagulov
2020-05-06 15:40 ` Henning Schild
2020-05-06 15:43 ` Jan Kiszka
2020-05-06 18:49 ` Baurzhan Ismagulov
2020-05-25 13:47 ` Baurzhan Ismagulov
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=20200505130234.0af1fc06@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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