From 982af6390208078cc5263ef24ac988f1eaeacfe9 Mon Sep 17 00:00:00 2001 From: Javier Viguera Date: Mon, 24 Feb 2014 12:26:42 +0100 Subject: [PATCH] meta-digi-arm: set branch absolute path to overcome fetcher bug bitbake git's fetcher uses 'ls-remote' to get the branch revision to checkout. If the repository has two branches ending equally the 'git ls-remote' just picks the first one regardless of that being the correct one. In our case we were bitten by this bug because our git repo has: ...sha1-revision... refs/heads/android/v3.10/master ...sha1-revision... refs/heads/v3.10/master and the fetcher was using the android branch instead of linux's v3.10/master. A patch has been sent upstream but while that gets applied to Dora maintenance branch the workaround here is to set the absolute path in the kernel's bitbake recipe. Signed-off-by: Javier Viguera --- meta-digi-arm/recipes-kernel/linux/linux-dey_3.10.bb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta-digi-arm/recipes-kernel/linux/linux-dey_3.10.bb b/meta-digi-arm/recipes-kernel/linux/linux-dey_3.10.bb index 7cf74c651..ac9fd99a8 100644 --- a/meta-digi-arm/recipes-kernel/linux/linux-dey_3.10.bb +++ b/meta-digi-arm/recipes-kernel/linux/linux-dey_3.10.bb @@ -7,7 +7,7 @@ PR = "${DISTRO}.${INC_PR}.0" DEPENDS += "lzop-native bc-native" -KBRANCH_DEFAULT = "v3.10/master" +KBRANCH_DEFAULT = "refs/heads/v3.10/master" KBRANCH = "${KBRANCH_DEFAULT}" KBRANCH_mxs = "v3.10.y/maint"