From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: erratic failure of pseudo
Date: Tue, 02 Aug 2011 11:11:52 +0100 [thread overview]
Message-ID: <1312279912.2344.574.camel@rex> (raw)
In-Reply-To: <840A81C1B782724A8EB52725BD519EFF181E0B@MBX20.4emm.local>
On Tue, 2011-08-02 at 07:28 +0000, James Limbouris wrote:
> Hi,
>
> I've just switched to oe-core from -dev, and I'm finding that my root
> images are showing incorrect permissions on files, randomly. From one
> build to the next, different subsets of files and folders end up owned
> by 1000:1000, instead of root:root. They aren't strictly grouped by
> package - just random files, different every time.
>
> Has anyone else noticed this behaviour? Does anyone have any advice on
> how to go about debugging? It might help to look at the pseudo db, and
> see if the permissions are in there - can anyone tell me where it is?
> I find an empty pseudo folder in the work folder after do_rm_work, but
> it is not there if I do a bitbake -c build image-xxx.
>
I'd work backwards with this. Check the owners of the files in the
packages, then that either points at the packages themselves or the
rootfs step. I'd also disable rm_work whilst debugging this since it
deletes a lot of the info you might want to use to debug it...
There is the PSEUDO_DEBUG=x environmental variable which can help with
pseudo debugging too...
Cheers,
Richard
next prev parent reply other threads:[~2011-08-02 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 7:28 erratic failure of pseudo James Limbouris
2011-08-02 10:11 ` Richard Purdie [this message]
2011-08-02 14:40 ` Mark Hatle
2011-08-03 3:57 James Limbouris
2011-08-05 3:20 James Limbouris
2011-08-06 7:33 James Limbouris
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=1312279912.2344.574.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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.