public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: wzh@ilbers.de, ziegler.andreas@siemens.com,
	jan.kiszka@siemen.com,
	Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v3 2/3] fix(container-loader): build one source package per architecture
Date: Mon, 10 Aug 2026 10:31:22 +0200	[thread overview]
Message-ID: <20260810083123.564384-3-felix.moessbauer@siemens.com> (raw)
In-Reply-To: <20260810083123.564384-1-felix.moessbauer@siemens.com>

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(+)

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"
 
-- 
2.55.0

-- 
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/20260810083123.564384-3-felix.moessbauer%40siemens.com.

  parent reply	other threads:[~2026-08-10  8:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-10  8:31 [PATCH v3 0/3] ensure source packages are deployed on rebuild with sstate 'Felix Moessbauer' via isar-users
2026-08-10  8:31 ` [PATCH v3 1/3] dpkg: let do_deploy_deb runtime depend on do_deploy_source 'Felix Moessbauer' via isar-users
2026-08-10  8:31 ` 'Felix Moessbauer' via isar-users [this message]
2026-08-10  8:31 ` [PATCH v3 3/3] dpkg: cache do_dpkg_source results in sstate 'Felix Moessbauer' via isar-users
2026-08-13 13:29   ` 'MOESSBAUER, Felix' via isar-users
2026-08-17  8:24     ` 'MOESSBAUER, Felix' via isar-users
2026-08-12 14:24 ` [PATCH v3 0/3] ensure source packages are deployed on rebuild with sstate Zhihang Wei

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=20260810083123.564384-3-felix.moessbauer@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemen.com \
    --cc=wzh@ilbers.de \
    --cc=ziegler.andreas@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