From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/3] wic: add fakeroot to the populate-extfs step
Date: Wed, 16 Oct 2013 13:09:00 +0100 [thread overview]
Message-ID: <1381925340.29912.461.camel@ted> (raw)
In-Reply-To: <3e3f7120140dc606369f19fbfca3e222db06274d.1381898855.git.tom.zanussi@linux.intel.com>
On Wed, 2013-10-16 at 00:14 -0500, Tom Zanussi wrote:
> Without this, files in the generated filesystem pick up the wrong
> ownership.
>
> Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
> ---
> scripts/lib/mic/kickstart/custom_commands/partition.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/lib/mic/kickstart/custom_commands/partition.py b/scripts/lib/mic/kickstart/custom_commands/partition.py
> index 302cace..309abee 100644
> --- a/scripts/lib/mic/kickstart/custom_commands/partition.py
> +++ b/scripts/lib/mic/kickstart/custom_commands/partition.py
> @@ -216,7 +216,7 @@ class Wic_PartData(Mic_PartData):
> """
> Prepare content for an ext2/3/4 rootfs partition.
> """
> - populate_script = "%s/usr/bin/populate-extfs.sh" % native_sysroot
> + populate_script = "fakeroot %s/usr/bin/populate-extfs.sh" % native_sysroot
> image_extra_space = 10240
>
> image_rootfs = rootfs_dir
We don't use fakeroot, please use pseudo. If pseudo doesn't work, we
need to figure out why and fix it.
Cheers,
Richard
next prev parent reply other threads:[~2013-10-16 12:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 5:14 [PATCH 0/3] a few wic fixes Tom Zanussi
2013-10-16 5:14 ` [PATCH 1/3] wic: check for build artifacts Tom Zanussi
2013-10-16 5:14 ` [PATCH 2/3] wic: check passed-in build artifact directories Tom Zanussi
2013-10-16 5:14 ` [PATCH 3/3] wic: add fakeroot to the populate-extfs step Tom Zanussi
2013-10-16 12:09 ` Richard Purdie [this message]
2013-10-16 15:10 ` Darren Hart
2013-10-16 15:36 ` Richard Purdie
2013-10-16 16:05 ` Darren Hart
2013-10-16 16:32 ` Richard Purdie
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=1381925340.29912.461.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=tom.zanussi@linux.intel.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