[v3,2/3] fix(container-loader): build one source package per architecture

Message ID 20260810083123.564384-3-felix.moessbauer@siemens.com
State Under Review
Headers show
Series ensure source packages are deployed on rebuild with sstate | expand

Commit Message

Felix Moessbauer Aug. 10, 2026, 8:31 a.m. UTC
We currently build architecture specific source packages with varying
content under the same name. This is not allowed in Debian, but remained
silently unnoticed as long as the packages are not deployed into the
same isar-apt.

As a preparation to cache the source packages, we need to ensure all
packages we build are either identical across all architectures, or are
architecture specific, along with having the arch in the package name.

Fixes: cd4e9090 ("container-loader: make generated package arch ...")
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta/classes-recipe/container-loader.bbclass | 5 +++++
 1 file changed, 5 insertions(+)

Patch

diff --git a/meta/classes-recipe/container-loader.bbclass b/meta/classes-recipe/container-loader.bbclass
index e5c82a74..8439db53 100644
--- a/meta/classes-recipe/container-loader.bbclass
+++ b/meta/classes-recipe/container-loader.bbclass
@@ -10,6 +10,11 @@  SRC_URI += " \
     file://container-loader.service.tmpl \
     file://container-loader.sh.tmpl"
 
+# make the source package architecture dependent to avoid
+# package collisions on multiconf / multiarch builds
+PROVIDES := "${BPN}"
+DEBIAN_PROVIDES := "${BPN}"
+PN .= "-${DISTRO_ARCH}"
 DPKG_ARCH ?= "${DISTRO_ARCH}"
 DEBIAN_MULTI_ARCH ?= "allowed"