From: "Hamza, Muhammad" <Muhammad_Hamza@mentor.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
Jacob Kroon <jacob.kroon@gmail.com>
Cc: "Larson, Chris" <Chris_Larson@mentor.com>
Subject: RE: [OE-core] [PATCH v1] glibc-locale: work around host-user-contaminated QA failure
Date: Thu, 16 Jun 2022 12:23:36 +0000 [thread overview]
Message-ID: <6ea7c38b8eba4df88666ee00a448ba7a@mentor.com> (raw)
In-Reply-To: <27226635e115be452ee7b5643860f4b53ee206b4.camel@linuxfoundation.org>
Hello, my bad, yes these changes are on some older branch and don't need upstream.
Thanks,
Hamza
-----Original Message-----
From: Richard Purdie <richard.purdie@linuxfoundation.org>
Sent: Thursday, June 16, 2022 3:23 PM
To: Hamza, Muhammad <Muhammad_Hamza@mentor.com>; openembedded-core@lists.openembedded.org
Cc: Larson, Chris <Chris_Larson@mentor.com>
Subject: Re: [OE-core] [PATCH v1] glibc-locale: work around host-user-contaminated QA failure
On Thu, 2022-06-16 at 10:54 +0500, Muhammad Hamza wrote:
> Work around long standing periodic host-user-contaminated QA failure
> by explicitly correcting the ownership.
>
> See `glibc-locale: Rewrite do_install using install utility instead of
> cp` on the oe-core mailing list for discussion. This should be dropped
> when a real fix is implemented.
>
> Explicitly disable host-user-contaminated to further work around the
> pseudo bug. With pseudo acting up, even if the ownership is correct,
> it may well think it is not, so just sidestep the issue until upstream
> fixes the root cause.
>
> Signed-off-by: Christopher Larson <chris_larson@mentor.com>
>
> Signed-off-by: Muhammad Hamza <muhammad_hamza@mentor.com>
> ---
> meta/recipes-core/glibc/glibc-locale.inc | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
> diff --git a/meta/recipes-core/glibc/glibc-locale.inc
> b/meta/recipes-core/glibc/glibc-locale.inc
> index b8de7d3192..34c178268b 100644
> --- a/meta/recipes-core/glibc/glibc-locale.inc
> +++ b/meta/recipes-core/glibc/glibc-locale.inc
> @@ -69,6 +69,23 @@ FILES:localedef = "${bindir}/localedef"
>
> LOCALETREESRC = "${COMPONENTS_DIR}/${PACKAGE_ARCH}/glibc-stash-locale"
>
> +# Work around long standing periodic host-user-contaminated QA
> +failure by # explicitly correcting the ownership.
> +#
> +# See `glibc-locale: Rewrite do_install using install utility instead
> +of cp` # on the oe-core mailing list for discussion. This should be
> +dropped when # a real fix is implemented.
> +
> +do_prep_locale_tree_append () {
> + chown -R root:root $treedir
> +}
> +
> +# Explicitly disable host-user-contaminated to further work around
> +the # pseudo bug. With pseudo acting up, even if the ownership is
> +correct, # it may well think it is not, so just sidestep the issue
> +until upstream # fixes the root cause.
> +ERROR_QA_remove = "host-user-contaminated"
> +
> copy_locale_files() {
> local dir=$1 mode=$2
At a quick search I couldn't find the email you reference so it probably isn't recent. As Jacob mentions, this syntax is invalid for master.
Was this not fixed properly by something like:
https://git.yoctoproject.org/poky/commit/?id=2e75c084f2cfe7617de3b9a4b006caa3fee687a6
?
We're definitely not taking this without more details on what is going on and a correct patch as this looks like a workaround.
Cheers,
Richard
prev parent reply other threads:[~2022-06-16 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 5:54 [PATCH v1] glibc-locale: work around host-user-contaminated QA failure Muhammad Hamza
2022-06-16 5:59 ` [OE-core] " Jacob Kroon
2022-06-16 10:23 ` Richard Purdie
2022-06-16 12:23 ` Hamza, Muhammad [this message]
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=6ea7c38b8eba4df88666ee00a448ba7a@mentor.com \
--to=muhammad_hamza@mentor.com \
--cc=Chris_Larson@mentor.com \
--cc=jacob.kroon@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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.