From: Benedikt Niedermayr <benbrenson89@googlemail.com>
To: Alexander Smirnov <asmirnov@ilbers.de>,
Jan Kiszka <jan.kiszka@siemens.com>,
isar-users <isar-users@googlegroups.com>
Subject: Re: PRoot: Drop sudo around buildchroot
Date: Wed, 25 Oct 2017 16:58:27 +0200 [thread overview]
Message-ID: <14315725-092a-8d1f-0c02-98efc30e7f2e@googlemail.com> (raw)
In-Reply-To: <f4094752-e10f-1ab1-e2b7-2169f18224f0@ilbers.de>
Am 25.10.2017 um 11:48 schrieb Alexander Smirnov:
>
>
> On 10/24/2017 11:22 PM, Jan Kiszka wrote:
>> On 2017-10-24 21:34, Alexander Smirnov wrote:
>>> Hello all,
>>>
>>> I've successfully dropped 'sudo' around buildchroot operations:
>>>
>>> - Create buildchroot
>>> - Build dpkg-base package (hello)
>>> - Build dpkg-raw package (example-raw)
>>>
>>> The patch is quite small, proot works out-of-the box. I've tested the
>>> following configurations:
>>>
>>> - multiconfig:qemuarm-wheezy:isar-image-base
>>> - multiconfig:qemuarm-jessie:isar-image-base
>>> - multiconfig:qemuarm-stretch:isar-image-base
>>> - multiconfig:qemui386-jessie:isar-image-base
>>> - multiconfig:qemui386-stretch:isar-image-base
>>> - multiconfig:qemuamd64-jessie:isar-image-base
>>> - multiconfig:qemuamd64-stretch:isar-image-base
>>>
>>> So proot is really good tool :-)
>>>
>>> If you'd like to reproduce the test, please try my branch:
>>> asmirnov/devel
>>>
>>> NOTE: do not forget to install proot: apt-get install proot
>>>
>>> Build command:
>>> $ bitbake multiconfig:qemuarm-wheezy:isar-image-base
>>> multiconfig:qemuarm-jessie:isar-image-base
>>> multiconfig:qemuarm-stretch:isar-image-base
>>> multiconfig:qemui386-jessie:isar-image-base
>>> multiconfig:qemui386-stretch:isar-image-base
>>> multiconfig:qemuamd64-jessie:isar-image-base
>>> multiconfig:qemuamd64-stretch:isar-image-base
>>>
>>
>> Great news! Hope this passes all tests and then makes it into master
>> soon!
>>
>
> I've tested QEMU machines for images listed above, no difference
> observed in comparison with original 'sudo' approach. But anyway, it
> would be nice if somebody else will test this, especially in customer
> project environment.
>
May there be a problem when all files belonging to the build user and
not to root?
Regards,
Benedikt
next prev parent reply other threads:[~2017-10-25 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 19:34 Alexander Smirnov
2017-10-24 20:22 ` Jan Kiszka
2017-10-25 9:48 ` Alexander Smirnov
2017-10-25 14:58 ` Benedikt Niedermayr [this message]
2017-10-25 15:29 ` Alexander Smirnov
2017-10-26 8:57 ` Ben Brenson
2017-11-02 17:19 ` Henning Schild
2017-11-02 17:22 ` Henning Schild
2017-11-03 9:00 ` Alexander Smirnov
2017-11-03 9:05 ` Jan Kiszka
2017-11-02 17:33 ` Jan Kiszka
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=14315725-092a-8d1f-0c02-98efc30e7f2e@googlemail.com \
--to=benbrenson89@googlemail.com \
--cc=asmirnov@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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