From: Martin Jansa <martin.jansa@gmail.com>
To: Armin Kuster <akuster808@gmail.com>
Cc: Armin Kuster <akuster@mvista.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH][jethro] glibc-locale: fix QA warning
Date: Fri, 1 Apr 2016 14:03:04 +0200 [thread overview]
Message-ID: <20160401120304.GE2567@jama> (raw)
In-Reply-To: <1454270130-11287-1-git-send-email-akuster808@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
On Sun, Jan 31, 2016 at 11:55:30AM -0800, Armin Kuster wrote:
> From: Armin Kuster <akuster@mvista.com>
>
> WARNING: QA Issue: glibc-locale: /glibc-binary-localedata-sd-in/usr/lib/locale/sd_IN/LC_CTYPE is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
FWIW: my last bitbke world build shows few of these:
glibc-locale-2.23: glibc-locale: /glibc-binary-localedata-ka-ge/usr/lib/locale/ka_GE/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]
glibc-locale-2.23: glibc-locale: /glibc-binary-localedata-mr-in/usr/lib/locale/mr_IN/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]
glibc-locale-2.23: glibc-locale: /glibc-binary-localedata-ru-ua/usr/lib/locale/ru_UA/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]
Even with your change already in master.
> fix type
> Signed-off-by: Armin Kuster <akuster@mvista.com>
> ---
> meta/recipes-core/glibc/glibc-locale.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/glibc/glibc-locale.inc b/meta/recipes-core/glibc/glibc-locale.inc
> index df6d073..2352bd0 100644
> --- a/meta/recipes-core/glibc/glibc-locale.inc
> +++ b/meta/recipes-core/glibc/glibc-locale.inc
> @@ -87,7 +87,7 @@ do_install () {
> if [ -e ${LOCALETREESRC}/${datadir}/locale ]; then
> cp -fpPR ${LOCALETREESRC}/${datadir}/locale ${D}${datadir}
> fi
> - chown root.root -R ${D}
> + chown root:root -R ${D}
> cp -fpPR ${LOCALETREESRC}/SUPPORTED ${WORKDIR}
> }
>
> --
> 2.3.5
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-04-01 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 19:55 [PATCH][jethro] glibc-locale: fix QA warning Armin Kuster
2016-02-07 22:43 ` Stable branch rules [Was: Re: [PATCH][jethro] glibc-locale: fix QA warning] Richard Purdie
2016-02-08 4:23 ` [Openembedded-architecture] " Khem Raj
2016-02-08 15:22 ` Joshua G Lock
2016-02-09 14:50 ` Philip Balister
2016-02-09 15:40 ` Joshua G Lock
2016-04-01 12:03 ` Martin Jansa [this message]
2016-04-01 13:14 ` [PATCH][jethro] glibc-locale: fix QA warning Richard Purdie
[not found] ` <56FEA982.5040500@mvista.com>
2016-04-02 18:19 ` 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=20160401120304.GE2567@jama \
--to=martin.jansa@gmail.com \
--cc=akuster808@gmail.com \
--cc=akuster@mvista.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