summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2012-11-29 13:42:22 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-12-03 15:23:18 +0000
commit57397592ff8ec16922604d398c18d53a589be41f (patch)
tree8b551807b913fc0fc025b7d68c32ea22b5ca1015
parent3230d943699c77f3fe9ce9d9949eae21d825186d (diff)
downloadopenembedded-core-57397592ff8ec16922604d398c18d53a589be41f.tar.gz
openembedded-core-57397592ff8ec16922604d398c18d53a589be41f.tar.bz2
openembedded-core-57397592ff8ec16922604d398c18d53a589be41f.zip
kernel-yocto: checkout known branch before leaving do_validate_branches
We should always leave the tree on a BSP branch or master when do_validate_branches completes to avoid modifying version tracked files are part of the build process. Modifying these files will lead to errors when changing branches, since the contents would be lost. This is evident in the case that a the meta branch is reset to a known SRCREV and the tree was left on the meta branch. This branch tracks the meta/meta-series, and other artifacts of the original tree construction. When the build process runs, it updates these same files, which creates a conflict when switching branches. This has been fixed in the tree construction scripts to not track these files, but a secondary fix is also required of not leaving the build on these branches, to allow arbitrary trees to be built. [YOCTO #3413] Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--meta/classes/kernel-yocto.bbclass2
1 files changed, 2 insertions, 0 deletions
diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index 0d4ed21e3a..c74317e9bd 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -327,6 +327,8 @@ do_validate_branches() {
if [ $? -eq 0 ]; then
# restore the branch for builds
git checkout -q -f ${KBRANCH}
+ else
+ git checkout -q master
fi
}