From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "Arjunan, Srinu" <srinuvasan.a@siemens.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Subject: Re: [cip-dev] [isar-cip-core] [PATCH 1/2] shtab: mark package as arch-all
Date: Mon, 15 Jun 2026 09:40:02 +0000 [thread overview]
Message-ID: <2ab1c9078bef00a746fef3a4e44dec675f408d84.camel@siemens.com> (raw)
In-Reply-To: <20260610212746.22275-1-srinuvasan.a@siemens.com>
On Thu, 2026-06-11 at 02:57 +0530, Srinuvasan A via lists.cip-
project.org wrote:
> From: srinuvasan <srinuvasan.a@siemens.com>
>
> Recent Isar cross-build profile changes add the
> `--no-arch-all` option to sbuild, causing shtab to fail
> during the build as it is an architecture-independent
> package.
>
> Set `DPKG_ARCH = "all"` to fix the build failure.
Right. Thanks for fixing this.
Reviewed-by: Felix Moessbauer <felix.moessbauer@siemens.com>
>
> Ref: https://github.com/ilbers/isar/commit/327fb313
>
> Signed-off-by: srinuvasan <srinuvasan.a@siemens.com>
> ---
> recipes-python/shtab/python-shtab_1.5.5-4.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/recipes-python/shtab/python-shtab_1.5.5-4.bb b/recipes-python/shtab/python-shtab_1.5.5-4.bb
> index 8ccef35..03e0aed 100644
> --- a/recipes-python/shtab/python-shtab_1.5.5-4.bb
> +++ b/recipes-python/shtab/python-shtab_1.5.5-4.bb
> @@ -11,6 +11,8 @@
>
> inherit dpkg-gbp
>
> +DPKG_ARCH = "all"
> +
> MAINTAINER = "cip-dev <cip-dev@lists.cip-project.org>"
>
> SRC_URI += " \
> --
> 2.39.5
prev parent reply other threads:[~2026-06-15 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 21:27 [isar-cip-core] [PATCH 1/2] shtab: mark package as arch-all srinuvasan.a
2026-06-10 21:27 ` [isar-cip-core] [PATCH 2/2] Update Isar revision srinuvasan.a
2026-06-16 7:44 ` Jan Kiszka
2026-06-15 9:40 ` MOESSBAUER, Felix [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=2ab1c9078bef00a746fef3a4e44dec675f408d84.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=srinuvasan.a@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