public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: christoph.steiger@siemens.com, gernot.hillier@siemens.com,
	cedric.hombourger@siemens.com
Subject: Re: [PATCH 1/1] always add architecture to binary packages in manifest
Date: Thu, 23 Oct 2025 09:57:25 +0200	[thread overview]
Message-ID: <c18ea478-10c4-40b6-81a1-7e7696385100@ilbers.de> (raw)
In-Reply-To: <20251013121540.388740-1-felix.moessbauer@siemens.com>

Applied to next, thanks.

Best regards,
Zhihang

On 10/13/25 14:15, 'Felix Moessbauer' via isar-users wrote:
> The manifest file contains the source / binary package relation and is
> helpful for license clearing. However, the binary package is only
> annotated with an architecture specified (:<arch>) if it otherwise
> cannot be uniquely identified on the generating system. As the consumer
> of that data is on a different system, this is not helpful. We now
> explicitly add the architecture specifier so that downstream consumers
> do not have to guess.
>
> Despite this slightly changes the output format, we don't consider this
> a breaking change, as the downstream consume anyways could not know
> which packages get the architecture specifier and which not, as this
> only depends on the package list of the target rootfs.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
>   meta/classes/rootfs.bbclass | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/rootfs.bbclass b/meta/classes/rootfs.bbclass
> index 12227db1..65779248 100644
> --- a/meta/classes/rootfs.bbclass
> +++ b/meta/classes/rootfs.bbclass
> @@ -399,7 +399,7 @@ rootfs_generate_manifest () {
>       mkdir -p ${ROOTFS_MANIFEST_DEPLOY_DIR}
>       sudo -E chroot --userspec=$(id -u):$(id -g) '${ROOTFSDIR}' \
>           dpkg-query -W -f \
> -            '${source:Package}|${source:Version}|${binary:Package}|${Version}\n' > \
> +            '${source:Package}|${source:Version}|${Package}:${Architecture}|${Version}\n' > \
>           '${ROOTFS_MANIFEST_DEPLOY_DIR}'/'${ROOTFS_PACKAGE_SUFFIX}'.manifest
>   }
>   

-- 
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/c18ea478-10c4-40b6-81a1-7e7696385100%40ilbers.de.

      reply	other threads:[~2025-10-23  7:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-13 12:15 'Felix Moessbauer' via isar-users
2025-10-23  7:57 ` Zhihang Wei [this message]

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=c18ea478-10c4-40b6-81a1-7e7696385100@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=cedric.hombourger@siemens.com \
    --cc=christoph.steiger@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=gernot.hillier@siemens.com \
    --cc=isar-users@googlegroups.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