public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: Anton Mikanovich <amikan@ilbers.de>,
	"Schmidl, Tobias" <tobiasschmidl@siemens.com>,
	Baurzhan Ismagulov <ibr@ilbers.de>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [PATCH v4 1/5] wic: Update to the latest revision
Date: Thu, 2 Jun 2022 07:44:05 +0000	[thread overview]
Message-ID: <AM9PR10MB4869E5AA5699990652BA00B489DE9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <63a4a7af-d037-36f0-dccd-6b53617e5c6e@ilbers.de>

> -----Original Message-----
> From: Anton Mikanovich <amikan@ilbers.de>
> Sent: Wednesday, June 1, 2022 4:10 PM
> To: Schmidl, Tobias (T CED SES-DE) <tobiasschmidl@siemens.com>;
> Moessbauer, Felix (T CED SES-DE) <felix.moessbauer@siemens.com>; isar-
> users@googlegroups.com; Baurzhan Ismagulov <ibr@ilbers.de>
> Subject: Re: [PATCH v4 1/5] wic: Update to the latest revision
> 
> 01.06.2022 15:22, Schmidl, Tobias wrote:
> > Hi all,
> >
> > Am Samstag, dem 28.05.2022 um 16:50 +0200 schrieb Felix Moessbauer:
> >> Update to the latest wic from OE-core.
> >>
> >> OE-core Revision: b8878cf0d35cf3d1ac30576d9b9943a7761c011b
> >>
> > how is the status of this patch? I have a pending patch that is
> > dependent on this one.
> >
> > Kind regards,
> >
> > Tobias
> >
> Hello,
> 
> This patch is ok to merge, but we have some issues with the new CI test case
> introduced in the same patchset. It is currently fails on one of our CI servers
> because of non working loop files mounting inside CI chroot.
> 
> I'm also not sure about do we need to introduce privileged operations like
> 'mount' inside testsuite. We need to get rid of sudo one day, and every new
> occurrence moves us away from the goal.

Maybe we should just drop these mounting tests until we have a proper solution.
It's just a patch and it should really not block the integration of the actual fix.

For me it is also ok to simply not include patch 5.

Felix

> 
> I think the most safe way is to use some tool like '7z l -ba <filename>' to list
> partition file content without mounting. But this will require to add it to Isar host
> tools requirements / kas image.

  reply	other threads:[~2022-06-02  7:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-28 14:50 [PATCH v4 0/5] " Felix Moessbauer
2022-05-28 14:50 ` [PATCH v4 1/5] " Felix Moessbauer
2022-06-01 12:22   ` Schmidl, Tobias
2022-06-01 14:10     ` Anton Mikanovich
2022-06-02  7:44       ` Moessbauer, Felix [this message]
2022-06-02 11:22         ` Anton Mikanovich
2022-05-28 14:50 ` [PATCH v4 2/5] meta-isar: add example how to split rootfs across partitions Felix Moessbauer
2022-05-28 14:50 ` [PATCH v4 3/5] use multipart image for qemuamd64-bookworm target Felix Moessbauer
2022-05-28 14:50 ` [PATCH v4 4/5] ci: test partition layout of splitted-rootfs image Felix Moessbauer
2022-05-28 14:50 ` [PATCH v4 5/5] ci: upload all logs from testsuite Felix Moessbauer
2022-06-03 15:53 ` [PATCH v4 0/5] wic: Update to the latest revision Anton Mikanovich

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=AM9PR10MB4869E5AA5699990652BA00B489DE9@AM9PR10MB4869.EURPRD10.PROD.OUTLOOK.COM \
    --to=felix.moessbauer@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=ibr@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=tobiasschmidl@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