public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Andreas Naumann' via isar-users" <isar-users@googlegroups.com>
To: "cedric.hombourger@siemens.com" <cedric.hombourger@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
Cc: "Steiger, Christoph" <christoph.steiger@siemens.com>,
	"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [PATCH 0/2] handle DPKG_ARCH=all case for transitive deps
Date: Mon, 27 Oct 2025 14:35:56 +0100	[thread overview]
Message-ID: <027334d6-a5ae-4893-a7ff-f6b9dcb7fc55@emlix.com> (raw)
In-Reply-To: <7b572ffbbd160f51fd15a737ff81c5278422e9ca.camel@siemens.com>

Hi all,

Am 24.10.25 um 07:34 schrieb 'cedric.hombourger@siemens.com' via isar-users:
> On Wed, 2025-08-20 at 14:41 +0200, Felix Moessbauer 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
>> 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.
> In my testing with downstream layers, this change caused some packages
> to be built for architectures they were not targeted for. For instance,
> I am now seeing the k3-rti-wdt firmware package [1] being built for
> both amd64 and arm64. I also had a dpkg-prebuilt recipe for a package
> supported on arm64 and amd64: it is now tried for armhf/i386.

Please have a look at the commit message of Patch 1 of my RFC I sent a 
while ago:

[PATCH 1/5] rootfs: Do not recursively deploy every dependent package

which I have now rephrased as "rootfs: Do not recursively build unneeded 
packages".

I think it's very likely that you're hit by the exact problem i describe 
there.

Later in the RFC i have suggested to drop the optimization part of this 
patch. Having reworked the series since, it's possible to even keep it. 
If you want, I can send the reworked version.

regards,
Andreas

>
> Then there was this issue with dpkg-customization packages now leading
> to a "multiple .bb files are due to be built" error. My work-around was
> to add DPKG_ARCH=any to the dpkg-customization class since
> customization packages are anyhow decorated with both DISTRO and
> MACHINE (it is therefore ok and possibly better to have them explicitly
> built for the arch of the MACHINE).
>
> Note: Jan had suggested that I also pull [2] but that did not help
>
> I evidently need to provide you more details. I have had a short
> discussion with Felix and we suspect that multiconfig builds may be
> causing these issues.
>
> Anyhow, I hope that I can create minimal reproducers and get them added
> to the CI test suite.
>
>> 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(-)
>>
-- 
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

-- 
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/027334d6-a5ae-4893-a7ff-f6b9dcb7fc55%40emlix.com.

      parent reply	other threads:[~2025-10-27 13:36 UTC|newest]

Thread overview: 21+ 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 [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=027334d6-a5ae-4893-a7ff-f6b9dcb7fc55@emlix.com \
    --to=isar-users@googlegroups.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=anaumann@emlix.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