* Re: [isar-cip-core][PATCH 0/4] make compatible with latest ISAR revision
[not found] <20231008031529.1338834-1-felix.moessbauer@siemens.com>
@ 2023-10-08 11:16 ` MOESSBAUER, Felix
0 siblings, 0 replies; only message in thread
From: MOESSBAUER, Felix @ 2023-10-08 11:16 UTC (permalink / raw)
To: cip-dev; +Cc: Schaffner, Tobias, Gylstorff, Quirin, Kiszka, Jan, isar-users
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(-)
>
^ permalink raw reply [flat|nested] only message in thread