From: "Alex Kiernan" <alex.kiernan@gmail.com>
To: Arnaud Pecoraro <arnaud.pecoraro@externs.easymile.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] rootfs-postcommands: Enable rootfs_check_host_user_contaminated
Date: Thu, 2 Apr 2020 14:39:10 +0100 [thread overview]
Message-ID: <CAO5Uq5QYE9Cn1DQxUtnKptqwyzpbUyY8dMaYMdwAm55yHj4mLQ@mail.gmail.com> (raw)
In-Reply-To: <CAM15ne=BtZqVdByS9VxHPSyDk+uAMVEWL6cQAaP8KXC_HX_DPA@mail.gmail.com>
On Wed, Apr 1, 2020 at 10:09 AM Arnaud Pecoraro
<arnaud.pecoraro@externs.easymile.com> wrote:
>
> Hello,
>
> We are having the same issue as described in the link below :
>
> https://lists.openembedded.org/g/openembedded-core/message?id=162040285
>
> WARNING: Paths in the rootfs are owned by the same user or group as the user running bitbake. See the logfile for the specific paths.
> /data/poky-tmp/master/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/rootfs/usr/share/fonts/.uuid
> /data/poky-tmp/master/work/intel_corei7_64-poky-linux/core-image-sato/1.0-r0/rootfs/usr/share/fonts/ttf/.uuid
>
> Any update on the patch?
>
If you've not pulled in the rootfs_check_host_user_contaminated check
(and it's not in master) then you shouldn't see this. Is it coming in
through another layer?
--
Alex Kiernan
next prev parent reply other threads:[~2020-04-02 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 9:09 [OE-core] rootfs-postcommands: Enable rootfs_check_host_user_contaminated arnaud.pecoraro
2020-04-02 13:39 ` Alex Kiernan [this message]
[not found] ` <CAM15nenPsBbL95RwC21UT9B7U0MY0y9pXYu+=-560C0tks=s6g@mail.gmail.com>
2020-04-03 15:19 ` Alex Kiernan
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=CAO5Uq5QYE9Cn1DQxUtnKptqwyzpbUyY8dMaYMdwAm55yHj4mLQ@mail.gmail.com \
--to=alex.kiernan@gmail.com \
--cc=arnaud.pecoraro@externs.easymile.com \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.