From: "'Niedermayr, BENEDIKT' via isar-users" <isar-users@googlegroups.com>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>,
"cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>,
"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
"Steiger, Christoph" <christoph.steiger@siemens.com>
Subject: Re: [PATCH 0/2] handle DPKG_ARCH=all case for transitive deps
Date: Fri, 31 Oct 2025 11:10:58 +0000 [thread overview]
Message-ID: <4ff5520e-1796-4309-aaef-6ca03f4c0669@siemens.com> (raw)
In-Reply-To: <20250820124140.281190-1-felix.moessbauer@siemens.com>
On 20.08.25 14:41, 'Felix Moessbauer' via isar-users wrote:
> This series fixes an issue with DPKG_ARCH=all packages that have
> dependencies to other DPKG_ARCH=all packages. Hereby, the transitive
> packages were built for the wrong architecture. The issue became
How can one reproduce this issue?
Isn't the architecture of an transitive dependency (when not using an
arch qualifier) derived from sbuild's "--host" parameter?
Regards,
Benedikt
> apparent when testing the SBOM series by Christoph, which builds
> packages to be used during the ISAR build (not for the final target).
>
> While fixing this, another issue surfaced where files are missing in
> dpkg-raw packages.
>
> Best regards,
> Felix
>
> Felix Moessbauer (2):
> dpkg-raw: add files to source package
> handle DPKG_ARCH=all case for transitive deps
>
> meta/classes/dpkg-raw.bbclass | 4 ++--
> meta/classes/multiarch.bbclass | 18 +++++++++++++++++-
> 2 files changed, 19 insertions(+), 3 deletions(-)
>
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/4ff5520e-1796-4309-aaef-6ca03f4c0669%40siemens.com.
prev parent reply other threads:[~2025-10-31 11:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 12:41 'Felix Moessbauer' via isar-users
2025-08-20 12:41 ` [PATCH 1/2] dpkg-raw: add files to source package 'Felix Moessbauer' via isar-users
2025-10-03 11:09 ` Anton Mikanovich
2025-08-20 12:41 ` [PATCH 2/2] handle DPKG_ARCH=all case for transitive deps 'Felix Moessbauer' via isar-users
2025-09-10 11:00 ` Andreas Naumann
2025-09-11 10:20 ` 'MOESSBAUER, Felix' via isar-users
2025-09-12 15:50 ` Andreas Naumann
2025-09-15 7:55 ` 'MOESSBAUER, Felix' via isar-users
2025-09-15 17:49 ` Andreas Naumann
2025-09-16 7:16 ` 'MOESSBAUER, Felix' via isar-users
2025-09-19 7:15 ` Andreas Naumann
2025-10-06 14:05 ` 'MOESSBAUER, Felix' via isar-users
2025-10-07 10:57 ` 'Andreas Naumann' via isar-users
2025-10-07 12:31 ` Zhihang Wei
2025-10-20 12:07 ` 'cedric.hombourger@siemens.com' via isar-users
2025-10-20 12:23 ` 'Jan Kiszka' via isar-users
2025-10-20 12:25 ` 'cedric.hombourger@siemens.com' via isar-users
2025-10-24 13:03 ` 'MOESSBAUER, Felix' via isar-users
2025-10-24 5:34 ` [PATCH 0/2] " 'cedric.hombourger@siemens.com' via isar-users
2025-10-24 7:36 ` 'MOESSBAUER, Felix' via isar-users
2025-10-27 13:35 ` 'Andreas Naumann' via isar-users
2025-10-31 11:10 ` 'Niedermayr, BENEDIKT' via isar-users [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=4ff5520e-1796-4309-aaef-6ca03f4c0669@siemens.com \
--to=isar-users@googlegroups.com \
--cc=adriaan.schmidt@siemens.com \
--cc=benedikt.niedermayr@siemens.com \
--cc=cedric.hombourger@siemens.com \
--cc=christoph.steiger@siemens.com \
--cc=felix.moessbauer@siemens.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