[OE-core] Cannot apply patches out of meta bsp after applied a kern-tool patch

[Bruce Ashfield]

On Thu, Sep 24, 2015 at 9:47 AM, Bruce Ashfield
<bruce.ashfield at gmail.com> wrote:
> On Thu, Sep 24, 2015 at 4:24 AM, LIYONG <sdliyong at gmail.com> wrote:
>> Hi all,
>>
>> After applied the below patch, bitbake cannot apply these patches in my app layer. For example, there is a kernel patch in meta-app/recipes-kernel/linux-yocto/linux-yocto, I add the file in linux-yocto_%.bbappend file. bitbake yocto-linux will fail with "do patch error". If I revert the patch, the build is okay.
>>
>> Any suggestions/comments?
>
> Raise a bug, and assign it to me. I can have a look at it. There must
> be some interaction in this configuration that I didn't test ... because I
> definiely did test the applcation of patches :)
>
> Make sure to add everything to the bug, the bbappend, the patch, etc,
> so I can re-create the failure on my machines.
>
> We can't revert that patch, since it actually is required to prevent patches
> from being applied multiple times .. so I'll need to incrementally fix the
> issue.

I just re-ran my test suite locally, and I'm able to apply patches
from my layers,
via bbappends.

So I'll need your details, and then I can debug further.

Bruce

>
> Bruce
>
>
>>
>> commit a03c100e813b1b5041bfc17c97f5bd4e72b795ad
>> Author: Bruce Ashfield <bruce.ashfield at windriver.com>
>> Date:   Mon Aug 31 15:55:33 2015 -0400
>>
>>     patching: only validate user supplied patches by default
>>
>>     Previously the patching tools would consider both system and user
>>     supplied patches in the same manner .. they are simply a series of
>>     patches to be applied to a branch, and that the scripts should determine
>>     where in the series to start (based on what is already on the branch).
>>
>>     This detection was causing a few problems:
>>
>>       - time consuming
>>       - starting in the middle of a series when intermediate patches were
>>         merged to a branch.
>>
>>     To solve both the performance and start detection, we instead simply
>>     note the transition from system (i.e. already defined features and
>>     series) and user/recipe supplied patches. When the transition is noted,
>>     the system will start pushing ALL patches without doing autoresume
>>     detection.
>>
>>     Control in keeping the series up to date is passed to the user, and
>> consistent behaviour/performance is achieved.
>>
>> Signed-off-by: Bruce Ashfield bruce.ashfield at windriver.com
>>
>>
>> Thanks,
>> Yong
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core at lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"