From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: SDK generation triggers quality_check warnings
Date: Wed, 13 Mar 2024 16:29:21 +0100 [thread overview]
Message-ID: <c2a32e2c-5360-4b10-a2e9-fc67eaa4f82b@siemens.com> (raw)
Hi all,
maybe someone has a quick idea what is causing this:
<select qemuamd64 target in the menu>
kas-container build -c populate_sdk
WARNING: isar-image-debug-sdk-1.0-r0 do_rootfs_quality_check: Files changed after package install. The following files seem
WARNING: isar-image-debug-sdk-1.0-r0 do_rootfs_quality_check: to have changed where they probably should not have.
WARNING: isar-image-debug-sdk-1.0-r0 do_rootfs_quality_check: You might have a custom task or writing POSTPROCESS function.
WARNING: isar-image-debug-sdk-1.0-r0 do_rootfs_quality_check: /build/tmp/work/debian-bookworm-amd64/isar-image-debug-sdk-qemuamd64/1.0-r0/rootfs/var/lib/dpkg/arch
Probably harmless but ugly.
There are likely other issues with host=target and customer DISTRO
names, but one after the other.
Jan
--
Siemens AG, Technology
Linux Expert Center
reply other threads:[~2024-03-13 15:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c2a32e2c-5360-4b10-a2e9-fc67eaa4f82b@siemens.com \
--to=jan.kiszka@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