diff options
| author | Bruce Ashfield <bruce.ashfield@windriver.com> | 2012-05-08 23:42:24 -0400 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-05-09 20:40:51 +0100 |
| commit | bd794b92d12ceda2728520701e980b7a3cabd23d (patch) | |
| tree | 962167b153ebde256d1e7b1a0cbe774f263cad93 /meta/recipes-support/libgcrypt | |
| parent | 87249372b4a9951f9e4dc6acece950718382a164 (diff) | |
| download | openembedded-core-bd794b92d12ceda2728520701e980b7a3cabd23d.tar.gz openembedded-core-bd794b92d12ceda2728520701e980b7a3cabd23d.tar.bz2 openembedded-core-bd794b92d12ceda2728520701e980b7a3cabd23d.tar.xz openembedded-core-bd794b92d12ceda2728520701e980b7a3cabd23d.zip | |
kern-tools: fix do_patch errors
The linux-yocto repository and scripts can support a mode of
meta data management that merges a base meta branch to every
BSP branch. In this case, the scripts don't have to restore
a checkpoint for the meta data to be globally accessible.
The decision to restore or not is made based on whether or
not the meta branch is part of all branches or not.
The linux-yocto recipes have a sanity check to determine if
the requested SRCREV for meta data matches the head of the
meta branch (via do_validate_branches). If the wrong commit
is at the head, the meta branch is moved aside and the branch
reset to the right commit. This creates two meta branches that
contain the base meta data.
The test for integrated meta data mistakes this for a globally
merged set of meta data and doesn't restore the checkpoint, which
leads to build failures.
The immediate fix is to allow two branches to have the meta
data. The long term fix is to make the detection only consider
if the build branch contains the meta data.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Diffstat (limited to 'meta/recipes-support/libgcrypt')
0 files changed, 0 insertions, 0 deletions