Digi
/
meta-digi
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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 <javier.viguera@digi.com>
This commit is contained in:
Javier Viguera 2014-02-24 12:26:42 +01:00
parent cfcc03beba
commit 982af63902
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
meta-digi-arm/recipes-kernel/linux/linux-dey_3.10.bb
View File

@ -7,7 +7,7 @@ PR = "${DISTRO}.${INC_PR}.0"
DEPENDS += "lzop-native bc-native" DEPENDS += "lzop-native bc-native"
KBRANCH_DEFAULT = "v3.10/master" KBRANCH_DEFAULT = "refs/heads/v3.10/master"
KBRANCH = "${KBRANCH_DEFAULT}" KBRANCH = "${KBRANCH_DEFAULT}"
KBRANCH_mxs = "v3.10.y/maint" KBRANCH_mxs = "v3.10.y/maint"