meta/recipes-bsp/trusted-firmware-a: use BPN for source package name

Message ID 20251120100340.419112-1-srinuvasan.a@siemens.com
State Under Review
Headers show
Series meta/recipes-bsp/trusted-firmware-a: use BPN for source package name | expand

Commit Message

srinuvasan.a Nov. 20, 2025, 10:03 a.m. UTC
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(-)

Patch

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}