From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"anaumann@emlix.com" <anaumann@emlix.com>
Cc: "Niedermayr, BENEDIKT" <benedikt.niedermayr@siemens.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"Koch, Stefan" <stefan-koch@siemens.com>
Subject: Re: [PATCH v2 2/2] propagate distro-specific dependencies of arch all packages
Date: Thu, 6 Nov 2025 12:13:30 +0000 [thread overview]
Message-ID: <67649f9484eba7fdc6ca69adf5d8f346efc1bbc9.camel@siemens.com> (raw)
In-Reply-To: <a1d770d4-288b-42db-9d1c-cd46f1e43adc@emlix.com>
On Thu, 2025-11-06 at 12:07 +0100, Andreas Naumann wrote:
> Hi Felix,
>
> Am 04.11.25 um 16:44 schrieb 'Felix Moessbauer' via isar-users:
> > DPKG_ARCH=all packages are always build in their -native variant.
> > However, these packages still can have non-native dependencies which
> > must be built for the distro arch.
> For me, this doesnt fix the testcase which I posted in my set on monday.
> So I'm surprised that it does for you, at least that's what i understood
> from your reply there. I was afraid gss wouldn't fail crosscompiling
> in trixie, but it does, at least for arm64.
There are currently so many moving bits (patches, kas bookworm vs kas
trixie environments, ...) it is hard to say what exactly worked and
what didn't.
> Now I reread your description carefully and assume it fixes something else
> than I had in mind. So short of info what the actual problem with
>
> 23a73895 ("multiarch: inject native variants of preferred providers")
>
> was, could you state it again? Do you have a specific testcase for it?
This problem was spotted in isar-cip-core when applying the
DPKG_ARCH=all transitive deps patch [1]. The problem hereby is that we
can no longer prefer-provide on the non native variant of a
DPKG_ARCH=all package. An example error message looks like the
following:
ERROR: Multiple .bb files are due to be built which each provide
secure-boot-secrets:
/work/build/../../repo/recipes-devtools/secure-boot-secrets/secure-
boot-snakeoil_0.3.bb
/work/build/../../repo/recipes-devtools/secure-boot-secrets/secure-
boot-key_0.2.bb
A list of tasks depending on these providers is shown and may help
explain where the dependency comes from.
Example kas file:
diff --git a/kas-cip.yml b/kas-cip.yml
index d76d6d94..4b18856d 100644
--- a/kas-cip.yml
+++ b/kas-cip.yml
@@ -22,7 +22,7 @@ repos:
isar:
url: https://github.com/ilbers/isar.git
- commit: d63a1cbae6f737aa843d00d8812547fe7b87104a
+ commit: 5a7c2f70045a27fe4073fa987ef07fe628062708
layers:
meta:
[1]
https://github.com/ilbers/isar/commit/5a7c2f70045a27fe4073fa987ef07fe628062708
Best regards,
Felix
> regards,
> Andreas
>
>
> > Fixes: 23a73895 ("multiarch: inject native variants of preferred providers")
> > Tested-by: Benedikt Niedermayr <benedikt.niedermayr@siemens.com>
> > Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> > ---
> > meta/classes/multiarch.bbclass | 10 ++++++----
> > 1 file changed, 6 insertions(+), 4 deletions(-)
> >
> > diff --git a/meta/classes/multiarch.bbclass b/meta/classes/multiarch.bbclass
> > index c2bba21f..74b8f5b8 100644
> > --- a/meta/classes/multiarch.bbclass
> > +++ b/meta/classes/multiarch.bbclass
> > @@ -106,11 +106,13 @@ python multiarch_virtclass_handler() {
> > # Arch=all packages might build depend on other arch=all packages,
> > # hence we need to correctly model the dependency chain.
> > # We implement this by dispatching the non-native variant to the -native
> > - # variant by adding a dependency. We further replace the non-native
> > - # do_deploy_dep task with a noop to preserve the dependency chain.
> > + # variant by adding a dependency. We further empty the non-native
> > + # do_deploy_dep task and clear the internal dependency chain, but keep
> > + # other attached variables like RDEPENDS to preserve the dependency chain.
> > e.data.setVar('do_deploy_deb', '')
> > - bb.build.deltask('deploy_deb', e.data)
> > - bb.build.addtask('deploy_deb', 'do_build', '', e.data)
> > + # clear internal dependencies (e.g. to do_dpkg_build)
> > + e.data.setVarFlag('do_deploy_deb', 'deps', [])
> > + # dispatch to native variant
> > e.data.setVarFlag('do_deploy_deb', 'depends', f'{pn}-native:do_deploy_deb')
> > }
> > addhandler multiarch_virtclass_handler
>
> --
> Andreas Naumann
>
> emlix GmbH
> Headquarters: Berliner Str. 12, 37073 Goettingen, Germany
> Phone +49 (0)551 30664-0, e-mail info@emlix.com
> District Court of Goettingen, Registry Number HR B 3160
> Managing Directors: Heike Jordan, Dr. Uwe Kracke
> VAT ID No. DE 205 198 055
> Office Berlin: Panoramastr. 1, 10178 Berlin, Germany
> Office Bonn: Bachstr. 6, 53115 Bonn, Germany
> http://www.emlix.com
--
Siemens AG
Linux Expert Center
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany
--
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/67649f9484eba7fdc6ca69adf5d8f346efc1bbc9.camel%40siemens.com.
next prev parent reply other threads:[~2025-11-06 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 15:44 [PATCH v2 1/2] do not add cross profile when building native package 'Felix Moessbauer' via isar-users
2025-11-04 15:44 ` [PATCH v2 2/2] propagate distro-specific dependencies of arch all packages 'Felix Moessbauer' via isar-users
2025-11-06 11:07 ` 'Andreas Naumann' via isar-users
2025-11-06 12:13 ` 'MOESSBAUER, Felix' via isar-users [this message]
2025-11-04 16:19 ` [PATCH v2 1/2] do not add cross profile when building native package 'Jan Kiszka' via isar-users
2025-11-04 18:24 ` 'MOESSBAUER, Felix' via isar-users
2025-11-06 8:47 ` 'MOESSBAUER, Felix' via isar-users
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=67649f9484eba7fdc6ca69adf5d8f346efc1bbc9.camel@siemens.com \
--to=isar-users@googlegroups.com \
--cc=anaumann@emlix.com \
--cc=benedikt.niedermayr@siemens.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=stefan-koch@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