Re: [PATCH v3 0/5] Fix single-name single-content rule for kernel packages

["'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>]

On Mon, 2026-08-24 at 12:49 +0200, Zhihang Wei wrote:
> On 8/20/26 10:03, 'Felix Moessbauer' via isar-users wrote:
> > Similar to upstream Debian, our kernel source packages are (among others)
> > architecture specific. By that, we also have to encode the architecture
> > (or machine) in the name of the package. Otherwise existing packages might
> > get reused on rebuilds with other targets (or multiarch)
> > 
> > In isar, this has ever been modeled incorrectly (the kernels .dsc file
> > was arch=any despite being arch specific). This is easy to fix, but
> > also depending on the kernels was done incorrectly (a KERNEL_NAME =
> > mainline is not specific enough, as mainline on arm64 is technically a
> > different kernel (source package) than mainline on amd64.
> > 
> > Patch 5 carries the implementation of option (1) from [1].
> > 
> > [1] https://groups.google.com/g/isar-users/c/JmB2FuEXZBU/m/azKokFVsAwAJ
> > 
> > The series has been tested in -t cross, -t kernel CI.
> > 
> > Changes since v2:
> > 
> > - improve commit messages according to Jan's feedback
> > - improve API changelog
> > - p2: drop redundant x86_64_defconfig
> > 
> > Changes since v1:
> > 
> > - no functional change
> > - rework API changelog and user manual
> > 
> > Best regards,
> > Felix Moessbauer
> > Siemens AG
> > 
> > Felix Moessbauer (5):
> >    testsuite: make test_libc_dev_deploy KERNEL_NAME agnostic
> >    kernel: bind x86_64_defconfig to amd64 architecture instead of machine
> >    kernel: make source package architecture specific
> >    kernel: move common parts of linux-mainline to inc
> >    kernel: use architecture specific names for kernels
> > 
> >   RECIPE-API-CHANGELOG.md                       |  4 ++
> >   doc/user_manual.md                            | 13 +++++-
> >   meta-isar/conf/machine/beagleplay.conf        |  2 +-
> >   meta-isar/conf/machine/de0-nano-soc.conf      |  2 +-
> >   meta-isar/conf/machine/hikey.conf             |  2 +-
> >   meta-isar/conf/machine/qemuamd64-cip.conf     |  2 +-
> >   meta-isar/conf/machine/sifive-fu540.conf      |  2 +-
> >   meta-isar/conf/machine/stm32mp15x.conf        |  2 +-
> >   .../linux/linux-cip_4.4.166-cip29.bb          |  7 ++-
> >   .../recipes-kernel/linux/linux-mainline.inc   | 45 +++++++++++++++++++
> >   .../linux/linux-mainline_6.12.85.bb           | 39 +---------------
> >   .../recipes-kernel/linux/linux-phy_6.12.85.bb |  2 +-
> >   meta/classes-recipe/linux-kernel.bbclass      |  3 +-
> >   .../linux-module/files/debian/control.tmpl    |  2 +-
> >   .../linux/files/debian/control.tmpl           | 10 ++---
> >   testsuite/citest.py                           | 23 +++++++---
> >   16 files changed, 99 insertions(+), 61 deletions(-)
> >   create mode 100644 meta-isar/recipes-kernel/linux/linux-mainline.inc
> > 
> 
> Hi,
> 
> The test case test_nocross in full failed. For example, when building the
> following two targets together using multiconfig:
> - "mc:qemuamd64-jammy:isar-image-base" and
> - "mc:qemuarm64-jammy:isar-image-base",

Hi,

found it. The module src package must not be architecture specific, as
this breaks on generic kernels like the one from Ubuntu.

This anyways is not needed anymore if kernels are named according to
their specifics (-arch / -machine).

Will send a v4 with p3 reverted (also due to the concerns brought up by
Jan).

Felix

> The following error occured:
> 
> [stdlog] 2026-08-21 11:09:21,148 avocado.app cibuilder        L0371 
> ERROR| ERROR: mc:qemuamd64-jammy:example-module-generic-1.0-r0 
> do_dpkg_build: 
> ExecutionError('/build/isar_wzh_devel_1z_others/49/build/tmp/work/ubuntu-jammy-amd64/example-module-generic/1.0-r0/temp/run.dpkg_runbuild.1650990', 
> 1, None, None)
> [stdlog] 2026-08-21 11:09:21,148 avocado.app cibuilder        L0371 
> ERROR| ERROR: Logfile of failure stored in: 
> /build/isar_wzh_devel_1z_others/49/build/tmp/work/ubuntu-jammy-amd64/example-module-generic/1.0-r0/temp/log.do_dpkg_build.1650990
> 
> In log.do_dpkg_build.1650990:
> <snip>
> +------------------------------------------------------------------------------+
> | Check architectures           |
> +------------------------------------------------------------------------------+
> 
> Initial Foreign Architectures: i386
> E: dsc: amd64 not in arch list or does not match any arch wildcards: 
> arm64 -- skipping
> 
> +------------------------------------------------------------------------------+
> | Cleanup           |
> +------------------------------------------------------------------------------+
> 
> Purging /<<BUILDDIR>>
> Not cleaning session: cloned chroot in use
> E: dsc: amd64 not in arch list or does not match any arch wildcards: 
> arm64 -- skipping
> 
> +------------------------------------------------------------------------------+
> | Summary           |
> +------------------------------------------------------------------------------+
> 
> Build Architecture: amd64
> Build Type: binary
> Build-Space: n/a
> Build-Time: 0
> Distribution: isar
> Fail-Stage: arch-check
> Foreign Architectures: i386
> Host Architecture: amd64
> Install-Time: 58
> Job: 
> /build/isar_wzh_devel_1z_others/49/build/tmp/deploy/isar-source/ubuntu-jammy/example-module-generic/example-module-generic_1.0.dsc
> Machine Architecture: amd64
> Package: example-module-generic
> Package-Time: 0
> Source-Version: 1.0
> Space: n/a
> Status: skipped
> Version: 1.0
> --------------------------------------------------------------------------------
> Finished at 2026-08-21T09:08:11Z
> Build needed 00:00:00, no disk space
> E: dsc: amd64 not in arch list or does not match any arch wildcards: 
> arm64 -- skipping
> cat: 
> /build/isar_wzh_devel_1z_others/49/build/tmp/work/ubuntu-jammy-amd64/example-module-generic/1.0-r0/rootfs/dpkg_partial.log: 
> No such file or directory
> WARNING: exit code 1 from a shell command.
> DEBUG: Executing shell function dpkg_chroot_finalize
> Removing 
> /etc/schroot/isar-jenkins-af6c5005-7b90-474f-9e3f-8358521a9208-1650990
> Removing 
> /etc/schroot/chroot.d/isar-jenkins-af6c5005-7b90-474f-9e3f-8358521a9208-1650990
> DEBUG: Shell function dpkg_chroot_finalize finished
> DEBUG: Python function do_dpkg_build finished
> 
> Zhihang
> 
> -- 
> 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/4db01ba4-f50e-44ed-a118-3badf0588c24%40ilbers.de.

-- 
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/b6957745472c7ff7ed2a53b3dc8484d5d56c37fe.camel%40siemens.com.