From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: "Moessbauer,
Felix (FT RPD CED OES-DE)" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 3/5] kernel: make source package architecture specific
Date: Thu, 20 Aug 2026 10:13:35 +0200 [thread overview]
Message-ID: <919b3679-f906-4970-8e25-ca2a4d4dcba3@siemens.com> (raw)
In-Reply-To: <0cd7141bb189d0b40496e472c51f32eae638497d.camel@siemens.com>
On 20.08.26 09:45, Moessbauer, Felix (FT RPD CED OES-DE) wrote:
> On Tue, 2026-08-18 at 08:23 +0200, Jan Kiszka wrote:
>> On 17.08.26 13:34, Felix Moessbauer wrote:>>> @@ -62,7 +62,7 @@ Description: ${KERNEL_NAME_PROVIDED} Linux kbuild
scripts and tools for @KR@
>>>
>>> Package: linux-kbuild-${KERNEL_NAME_PROVIDED}-${DISTRO_ARCH}-cross
>>> Build-Profiles: <pkg.${BPN}.kbuild pkg.${BPN}.cross>
>>> -Architecture: any
>>> +Architecture: ${BUILD_ARCH}
>>> Multi-Arch: foreign
>>> Depends: ${perl:Depends}, ${shlibs:Depends}
>>> Conflicts: linux-kbuild-${KERNEL_NAME_PROVIDED}
>>
>> And for linux-kbuild, it uses the architecture "linux-any" - what's that?
>
> That's the wildcard for any architecture that uses Linux (in contrast
> to any, which would also match gnu-hurd / hurd-i386). As we are Linux
> only anyways, this should not matter for us.
>
In other words, Debian uses "any" here.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
--
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/919b3679-f906-4970-8e25-ca2a4d4dcba3%40siemens.com.
next prev parent reply other threads:[~2026-08-20 8:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 11:34 [PATCH v2 0/5] Fix single-name single-content rule for kernel packages 'Felix Moessbauer' via isar-users
2026-08-17 11:34 ` [PATCH v2 1/5] testsuite: make test_libc_dev_deploy KERNEL_NAME agnostic 'Felix Moessbauer' via isar-users
2026-08-17 11:34 ` [PATCH v2 2/5] kernel: bind x86_64_defconfig to amd64 architecture instead of machine 'Felix Moessbauer' via isar-users
2026-08-18 6:27 ` 'Jan Kiszka' via isar-users
2026-08-17 11:34 ` [PATCH v2 3/5] kernel: make source package architecture specific 'Felix Moessbauer' via isar-users
2026-08-18 6:23 ` 'Jan Kiszka' via isar-users
2026-08-20 7:45 ` 'MOESSBAUER, Felix' via isar-users
2026-08-20 8:13 ` 'Jan Kiszka' via isar-users [this message]
2026-08-20 8:29 ` 'MOESSBAUER, Felix' via isar-users
2026-08-17 11:34 ` [PATCH v2 4/5] kernel: move common parts of linux-mainline to inc 'Felix Moessbauer' via isar-users
2026-08-17 11:34 ` [PATCH v2 5/5] kernel: use architecture specific names for kernels 'Felix Moessbauer' via isar-users
2026-08-18 6:26 ` 'Jan Kiszka' via isar-users
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=919b3679-f906-4970-8e25-ca2a4d4dcba3@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@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