From: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
To: "cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Cc: "Schaffner, Tobias" <tobias.schaffner@siemens.com>,
"Gylstorff, Quirin" <quirin.gylstorff@siemens.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [isar-cip-core][PATCH 0/4] make compatible with latest ISAR revision
Date: Sun, 8 Oct 2023 11:16:40 +0000 [thread overview]
Message-ID: <be41f36b6bb8a295a01115ff82e692430725c441.camel@siemens.com> (raw)
In-Reply-To: <20231008031529.1338834-1-felix.moessbauer@siemens.com>
On Sun, 2023-10-08 at 11:15 +0800, Felix Moessbauer wrote:
> This series adapts the imager parts of cip-core to the new schroot-
> based
> imaging in ISAR. This change is required to make it compatible with
> the latest
> master branch of ISAR. Finally, the ISAR version is bumped.
While testing this on a broader scope, I noticed that in some cases the
image users are not created correctly (the user is created according to
/etc/passwd, but the password does not work).
I can reliably reproduce this on an internal target, but unfortunately
this requires also real hardware. The affected image uses swupdate with
ebg.
Is there any recent change in ISAR which effects the point in time when
users are created? Putting the ISAR ML in CC.
Felix
>
> Note: This series depends on "drop dependency to no longer existing
> buildchroot".
>
> Best regards,
> Felix Moessbauer
>
> Felix Moessbauer (4):
> make deploy-ovmf compatible with schroot imaging
> make swupdate class compatible with schroot imaging
> avoid use of sudo when creating squashfs
> update ISAR to latest version on master branch
>
> classes/squashfs.bbclass | 2 +-
> classes/swupdate.bbclass | 5 +++--
> kas-cip.yml | 2 +-
> recipes-core/images/deploy-ovmf.inc | 10 +++++++---
> 4 files changed, 12 insertions(+), 7 deletions(-)
>
parent reply other threads:[~2023-10-08 11:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20231008031529.1338834-1-felix.moessbauer@siemens.com>]
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=be41f36b6bb8a295a01115ff82e692430725c441.camel@siemens.com \
--to=felix.moessbauer@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@siemens.com \
--cc=tobias.schaffner@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