From: Zhihang Wei <wzh@ilbers.de>
To: srinuvasan.a@siemens.com, isar-users@googlegroups.com
Subject: Re: [PATCH] meta/recipes-bsp/trusted-firmware-a: use BPN for source package name
Date: Wed, 26 Nov 2025 10:46:44 +0100 [thread overview]
Message-ID: <05167df5-6cb0-48c6-b7a3-cb8e6057b2a6@ilbers.de> (raw)
In-Reply-To: <20251120100340.419112-1-srinuvasan.a@siemens.com>
Applied to next, thanks.
On 11/20/25 11:03, srinuvasan.a via isar-users wrote:
> From: Srinuvasan A <srinuvasan.a@siemens.com>
>
> When building the -native recipe, the build fails due to conflicting
> source package identifiers. Using the base package name (BPN) ensures a
> consistent source name for both native and non-native variants, resolving
> the conflict.
>
> Err Logs:
> DEBUG: Executing shell function do_dpkg_source
> dpkg-source: warning: no source format specified in debian/source/format, see dpkg-source(1)
> dpkg-source: error: source package has two conflicting values - trusted-firmware-a-iot2050-native and trusted-firmware-a-iot2050
> WARNING: exit code 2 from a shell command.
>
> Signed-off-by: Srinuvasan A <srinuvasan.a@siemens.com>
> ---
> meta/recipes-bsp/trusted-firmware-a/files/debian/control.tmpl | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-bsp/trusted-firmware-a/files/debian/control.tmpl b/meta/recipes-bsp/trusted-firmware-a/files/debian/control.tmpl
> index 903da980..bb21b6e5 100644
> --- a/meta/recipes-bsp/trusted-firmware-a/files/debian/control.tmpl
> +++ b/meta/recipes-bsp/trusted-firmware-a/files/debian/control.tmpl
> @@ -1,4 +1,4 @@
> -Source: ${PN}
> +Source: ${BPN}
> Section: admin
> Priority: optional
> Standards-Version: ${DEBIAN_STANDARDS_VERSION}
--
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/05167df5-6cb0-48c6-b7a3-cb8e6057b2a6%40ilbers.de.
prev parent reply other threads:[~2025-11-26 9:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 10:03 srinuvasan.a via isar-users
2025-11-26 9:46 ` Zhihang Wei [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=05167df5-6cb0-48c6-b7a3-cb8e6057b2a6@ilbers.de \
--to=wzh@ilbers.de \
--cc=isar-users@googlegroups.com \
--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