Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] libc-package.bbclass: Correct a few paths for when usrmerge is used
Date: Sun, 17 Feb 2019 22:52:52 +0000	[thread overview]
Message-ID: <eb8026185baf26c376b24633aae735c8f2076602.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190217145107.2796-1-pkj@axis.com>

On Sun, 2019-02-17 at 15:51 +0100, Peter Kjellerstedt wrote:
> Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> ---
>  meta/classes/libc-package.bbclass | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

I included this patchset in a run on the autobuilder and its failing:

https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/66

I know the resulttool failures are my fault but the glibc-locale ones
aren't. I'll abort the build as there are enough failures to know its
doomed and I need a results set for other testing.

Cheers,

Richard



  parent reply	other threads:[~2019-02-17 22:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17 14:51 [PATCH 1/3] libc-package.bbclass: Correct a few paths for when usrmerge is used Peter Kjellerstedt
2019-02-17 14:51 ` [PATCH 2/3] libc-package.bbclass: Only extract wanted files in prep_locale_tree() Peter Kjellerstedt
2019-02-17 14:51 ` [PATCH 3/3] libc-package.bbclass: Add a progress meter for the package task Peter Kjellerstedt
2019-02-18  1:21   ` Christopher Larson
2019-02-18  1:37     ` Peter Kjellerstedt
2019-02-17 22:52 ` Richard Purdie [this message]
2019-02-19  7:03   ` [PATCH 1/3] libc-package.bbclass: Correct a few paths for when usrmerge is used Khem Raj

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=eb8026185baf26c376b24633aae735c8f2076602.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.com \
    /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