From: Koen Kooi <koen.kooi@linaro.org>
To: Otavio Salvador <otavio@ossystems.com.br>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC][PATCH] package.bbclass: fix strip and split logic
Date: Tue, 04 Feb 2014 12:27:23 +0100 [thread overview]
Message-ID: <52F0CE9B.7060601@linaro.org> (raw)
In-Reply-To: <CAP9ODKr7Ypt08VYjnZ=1rmmwh-Ri+qjWwc4L9yiF=iw8dE2ArQ@mail.gmail.com>
On 02/04/2014 12:20 PM, Otavio Salvador wrote:
> Hello Richard,
>
> On Tue, Feb 4, 2014 at 7:32 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
>> 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.
>
> I asked two fixes for Koen in the patch and I am awaiting this to
> apply his patches.
And I already said I'm not planning to jump through more hoops just to
get this patch into OE-core.
--
Koen Kooi
Builds and Baselines | Release Manager
Linaro.org | Open source software for ARM SoCs
next prev parent reply other threads:[~2014-02-04 11:27 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
2014-02-04 11:20 ` Otavio Salvador
2014-02-04 11:27 ` Koen Kooi [this message]
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=52F0CE9B.7060601@linaro.org \
--to=koen.kooi@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox