From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 0/9] first wic integration
Date: Wed, 31 Jan 2018 13:02:46 +0100 [thread overview]
Message-ID: <20180131120245.GC6508@yssyq.radix50.net> (raw)
In-Reply-To: <675eeef9-1e24-4784-b894-4ce665da26fb@siemens.com>
On Wed, Jan 31, 2018 at 12:47:08PM +0100, Jan Kiszka wrote:
> >> If the manual non-root call did work before, i will look into that.
> >
> > Yes. Yes, please do.
> >
> > In Yocto, manual non-root call works. The same is our vision for Isar. For now,
> > it has been workarounded with sudo. We have a working PoC based on PRoot in the
> > pipeline. So I don't support the idea of changing the user experience because
> > of this issue.
>
> While I agree we should try to get whole Isar unprivileged, let's not
> invest too much into this when it's complex. We are currently far away
> from that goal (as you know, proot has several open issues as well), and
> this here solves the problem of having to run wic manually at all.
No effort whatsoever. This is already workarounded in master in the following
commit:
bf873d3 wic: Use sudo instead of pseudo
My suggestion is not to revert that. I agree with Henning that we should cover
that in CI. I'll provide an initial testing framework, then we should sync who
does what. The other mcopy and fsck issues are not covered, either.
Regarding the PRoot PoC, I don't agree we are far away. Everything works
except mounting. We've just postponed the work due to higher-prio issues.
> > b1511ec wic: Work around mcopy error
> > 17f9196 wic: Introduce the `WicExecError` exception class
> >
> > All of them are not related to the bitbake core and fix concrete issues with
> > image generation that were not addressed in the baseline bitbake. Did you
> > address those issues in your new changes?
>
> Good points, should be clarified. Maybe an update of the upstream wic
> import is the answer if we are about to lose something. Better than
> patching locally in Isar, as so far.
Do you mean we should initiate upstreaming that to OE? If yes, I agree with
you. The only question is point of time. My idea was to wait till Henning
completes the lifecycle with his OE contribution and learn from his experience.
If you think we should do that now, please let me know.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2018-01-31 12:02 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 9:41 Henning Schild
2018-01-31 9:41 ` [PATCH 1/9] classes: image: introduce size measuring function, for before do_*_image Henning Schild
2018-01-31 9:41 ` [PATCH 2/9] images: new class wic-img for wic intregration Henning Schild
2018-02-13 14:44 ` Alexander Smirnov
2018-02-13 16:06 ` Henning Schild
2018-01-31 9:41 ` [PATCH 3/9] wic: add a bootimg-efi-isar plugin outside the wic tree Henning Schild
2018-02-12 17:48 ` Jan Kiszka
2018-01-31 9:41 ` [PATCH 4/9] Revert "wic: Make the bootimg-efi plugin generate usable images" Henning Schild
2018-01-31 9:41 ` [PATCH 5/9] Revert "wic: Introduce the `WicExecError` exception class" Henning Schild
2018-01-31 9:41 ` [PATCH 6/9] Revert "wic: Work around mcopy error" Henning Schild
2018-01-31 9:41 ` [PATCH 7/9] Revert "wic: Use sudo instead of pseudo" Henning Schild
2018-01-31 9:41 ` [PATCH 8/9] Revert "wic: Remove sysroot support" Henning Schild
2018-01-31 9:42 ` [PATCH 9/9] wic: now truly go for the wic version we claim to have Henning Schild
2018-01-31 10:11 ` Alexander Smirnov
2018-01-31 10:55 ` Jan Kiszka
2018-01-31 11:11 ` Alexander Smirnov
2018-01-31 11:43 ` Jan Kiszka
2018-01-31 11:53 ` Baurzhan Ismagulov
2018-01-31 12:01 ` Jan Kiszka
2018-01-31 12:28 ` Baurzhan Ismagulov
2018-01-31 13:53 ` Henning Schild
2018-01-31 14:01 ` Baurzhan Ismagulov
2018-01-31 14:21 ` Henning Schild
2018-01-31 10:02 ` [PATCH 0/9] first wic integration Alexander Smirnov
2018-01-31 10:12 ` Henning Schild
2018-01-31 11:24 ` Baurzhan Ismagulov
2018-01-31 11:47 ` Jan Kiszka
2018-01-31 12:02 ` Baurzhan Ismagulov [this message]
2018-01-31 12:15 ` Jan Kiszka
2018-01-31 13:30 ` Jan Kiszka
2018-01-31 13:41 ` Baurzhan Ismagulov
2018-01-31 14:01 ` Jan Kiszka
2018-01-31 15:21 ` Baurzhan Ismagulov
2018-01-31 15:46 ` Henning Schild
2018-01-31 16:13 ` Jan Kiszka
2018-01-31 13:35 ` Baurzhan Ismagulov
2018-01-31 13:47 ` Henning Schild
2018-01-31 14:00 ` Baurzhan Ismagulov
2018-01-31 13:46 ` Henning Schild
2018-01-31 13:36 ` Henning Schild
2018-01-31 13:40 ` Baurzhan Ismagulov
2018-01-31 13:05 ` Henning Schild
2018-02-01 12:41 ` [PATCH] images: wic: limit use of sudo and enable manual call again Henning Schild
2018-02-01 12:44 ` Henning Schild
2018-02-01 16:09 ` Baurzhan Ismagulov
2018-02-01 18:10 ` Henning Schild
2018-02-01 18:55 ` Henning Schild
2018-02-12 19:07 ` Henning Schild
2018-02-12 17:27 ` [PATCH 0/9] first wic integration Henning Schild
2018-02-12 18:21 ` Alexander Smirnov
2018-02-12 18:30 ` Henning Schild
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=20180131120245.GC6508@yssyq.radix50.net \
--to=ibr@radix50.net \
--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