From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Koen Kooi <koen.kooi@linaro.org>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
openembedded-core@lists.openembedded.org
Subject: Re: [RFC][PATCH] package.bbclass: fix strip and split logic
Date: Tue, 04 Feb 2014 09:32:05 +0000 [thread overview]
Message-ID: <1391506325.22620.12.camel@ted> (raw)
In-Reply-To: <52F0ABC7.1010908@linaro.org>
On Tue, 2014-02-04 at 09:58 +0100, Koen Kooi wrote:
> On 01/21/2014 04:09 PM, Richard Purdie wrote:
> > On Tue, 2014-01-21 at 15:03 +0100, Koen Kooi wrote:
> >> On 01/21/2014 02:57 PM, Richard Purdie wrote:
> >>> On Tue, 2014-01-21 at 10:47 +0100, Koen Kooi wrote:
> > I'm ok with it in principle but I'd like to see known build issues fixed
> > before it goes in since red autobuilders cause me enough grief
> > already ;-).
>
> What's the status on this? I know a fix went into meta-intel (albeit it
> in a legally questionable way, but that's their problem) and the other
> affected layers have received patches for it.
The last test build I ran:
http://autobuilder.yoctoproject.org/main/builders/nightly-fsl-arm/builds/10/steps/BuildImages_1/logs/stdio
still shows an error in the fsl-arm layer which I suspect is from this.
I was hoping that could get fixed before it merges, its very much still
in the queue though.
I won't wait forever, equally, maintaining the green builds is proving
to consume a lot of my time and if I can avoid adding more failures, I'd
prefer to do so.
Cheers,
Richard
next prev parent reply other threads:[~2014-02-04 9:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 9:47 [RFC][PATCH] package.bbclass: fix strip and split logic Koen Kooi
2014-01-21 13:57 ` Richard Purdie
2014-01-21 14:03 ` Koen Kooi
2014-01-21 15:04 ` Mark Hatle
2014-01-21 15:09 ` Richard Purdie
2014-01-23 9:34 ` Koen Kooi
2014-01-23 11:33 ` Otavio Salvador
2014-01-23 12:41 ` Martin Jansa
2014-02-04 8:58 ` Koen Kooi
2014-02-04 9:32 ` Richard Purdie [this message]
2014-02-04 11:20 ` Otavio Salvador
2014-02-04 11:27 ` Koen Kooi
2014-02-04 12:12 ` Otavio Salvador
2014-02-04 10:10 ` Paul Eggleton
2014-02-04 11:01 ` Koen Kooi
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=1391506325.22620.12.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen.kooi@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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