public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'cedric.hombourger@siemens.com' via isar-users" <isar-users@googlegroups.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>,
	"wzh@ilbers.de" <wzh@ilbers.de>,
	"MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
Cc: "Steiger, Christoph" <christoph.steiger@siemens.com>,
	"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
Subject: Re: [PATCH 2/2] handle DPKG_ARCH=all case for transitive deps
Date: Mon, 20 Oct 2025 12:25:52 +0000	[thread overview]
Message-ID: <304522592621eaf678f47b711604c65eccfe29da.camel@siemens.com> (raw)
In-Reply-To: <d1a2da82-2af3-42df-bf79-11b4085a3276@siemens.com>

On Mon, 2025-10-20 at 14:23 +0200, Jan Kiszka wrote:
> On 20.10.25 14:07, Hombourger, Cedric (FT FDS CES LX) wrote:
> > On Tue, 2025-10-07 at 14:31 +0200, Zhihang Wei wrote:
> > > p2 was applied to next, thanks.
> >
> > this appears to cause a regression with dpkg-customization
> > packages.
> > Not yet sure why this wasn't caught by dpkg-customization test
> > cases
> > that Chris had added when dpkg-customization was introduced.
> >
> > ERROR: Multiple .bb files are due to be built which each provide
> > hostname-customization:
> >   mc:iot2050-bookworm:/work/build/../isar/meta/recipes-
> > support/customizations/hostname-customization.bb
> >   mc:iot2050-
> > bookworm:virtual:native:/work/build/../isar/meta/recipes-
> > support/customizations/hostname-customization.bb
> > A list of tasks depending on these providers is shown and may help
> > explain where the dependency comes from.
> > mc:iot2050-bookworm:/work/build/../isar/meta/recipes-
> > support/customizations/hostname-customization.bb has unique
> > dependees:
> >   mc:iot2050-
> > bookworm:virtual:native:/work/build/../isar/meta/recipes-
> > support/customizations/hostname-customization.bb:do_dpkg_build
> >   mc:iot2050-bookworm:/work/build/../../repo/meta/recipes-
> > core/images/development-image.bb:do_image_tools
> >   mc:iot2050-
> > bookworm:virtual:native:/work/build/../isar/meta/recipes-
> > support/customizations/hostname-
> > customization.bb:do_fetch_common_source
> > mc:iot2050-
> > bookworm:virtual:native:/work/build/../isar/meta/recipes-
> > support/customizations/hostname-customization.bb has unique
> > dependees:
> >   mc:iot2050-bookworm:/work/build/../isar/meta/recipes-
> > support/customizations/hostname-customization.bb:do_deploy_deb
> > It could be that one recipe provides something the other doesn't
> > and
> > should. The following provider and runtime provider differences may
> > be
> > helpful.
> > mc:iot2050-bookworm:/work/build/../isar/meta/recipes-
> > support/customizations/hostname-customization.bb has unique
> > provides:
> >   bookworm-hostname-customization-iot2050
> > mc:iot2050-bookworm:/work/build/../isar/meta/recipes-
> > support/customizations/hostname-customization.bb has unique
> > rprovides:
> >   hostname-customization
> >   bookworm-hostname-customization-iot2050
> > mc:iot2050-
> > bookworm:virtual:native:/work/build/../isar/meta/recipes-
> > support/customizations/hostname-customization.bb has unique
> > provides:
> >   bookworm-hostname-customization-iot2050-native
> > mc:iot2050-
> > bookworm:virtual:native:/work/build/../isar/meta/recipes-
> > support/customizations/hostname-customization.bb has unique
> > rprovides:
> >   bookworm-hostname-customization-iot2050-native
> >
>
> Will be fixed once
> https://patchwork.isar-build.org/project/isar/patch/20251017085344.2647058-1-felix.moessbauer@siemens.com/
> is merged - hopefully rather sooner than later.

Ah thanks Jan!

I am reworking the customization patch without that patch hoping to
catch the same failure. Will then apply the suggested patch and
hopefully confirm the fix. I would then post the patch for the
testsuite.

>
> Jan
>

--
Cedric Hombourger
Siemens AG
http://www.siemens.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/304522592621eaf678f47b711604c65eccfe29da.camel%40siemens.com.

  reply	other threads:[~2025-10-20 12:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-20 12:41 [PATCH 0/2] " '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 [this message]
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

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=304522592621eaf678f47b711604c65eccfe29da.camel@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=adriaan.schmidt@siemens.com \
    --cc=cedric.hombourger@siemens.com \
    --cc=christoph.steiger@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=wzh@ilbers.de \
    /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