From: Seebs <seebs@seebs.net>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH] insane.bbclass: Add do_qa_pseudo function to check for common errors listed in pseudo.log
Date: Thu, 14 Sep 2017 09:27:50 -0500 [thread overview]
Message-ID: <20170914092750.19cedd67@seebsdell> (raw)
In-Reply-To: <CA+chaQcxHMzTwiAEQx4zPkVrbLHndUoVVS=yWz=hiOE43VZzNg@mail.gmail.com>
On Thu, 14 Sep 2017 00:28:34 +0200
Martin Jansa <martin.jansa@gmail.com> wrote:
> OK, thanks.
>
> Any insights to the first issue described in commit message? That we
> know that is an Actual Problem, but hard to reproduce it.
This one?
glibc-locale-2.26:
glibc-locale: /glibc-binary-localedata-en-gb/usr/lib/locale/en_GB/LC_MEASUREMENT
is owned by uid 3004, which is the same as the user running bitbake.
This may be due to host contamination [host-user-contaminated]
My first guess would be some kind of weird timing interaction involving
symlinks or, if it's still there, the really weird copy of locale data
into an intermediate location to move it from the glibc package to the
glibc_locale package or something. But it seems like that should be
reproducible, so I'm not sure.
-s
next prev parent reply other threads:[~2017-09-14 14:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 20:46 [RFC][PATCH] insane.bbclass: Add do_qa_pseudo function to check for common errors listed in pseudo.log Martin Jansa
2017-09-13 20:50 ` Martin Jansa
2017-09-13 22:08 ` Seebs
2017-09-13 22:28 ` Martin Jansa
2017-09-14 14:27 ` Seebs [this message]
2017-09-14 13:17 ` Burton, Ross
2017-09-13 22:09 ` Seebs
2017-09-14 14:53 ` Burton, Ross
2017-09-14 14:59 ` Seebs
2017-09-19 15:18 ` [RFC][PATCHv2] " Martin Jansa
2017-10-16 15:01 ` Martin Jansa
2017-10-16 15:10 ` Burton, Ross
2017-10-16 15:50 ` Martin Jansa
2017-12-19 16:09 ` Martin Jansa
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=20170914092750.19cedd67@seebsdell \
--to=seebs@seebs.net \
--cc=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox