Bug 9353

Summary: yocto-bsp: script using different kernel than the one given when creating bsp
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Humberto Ibarra <humberto.ibarra.lopez>
Component: Scripts and ToolsAssignee: Humberto Ibarra <humberto.ibarra.lopez>
Status: RESOLVED FIXED QA Contact: Francisco Pedraza <francisco.j.pedraza.gonzalez>
Severity: normal    
Priority: Medium+ CC: benjamin.esquivel, leonardo.sandoval.gonzalez, ross.burton
Version: 2.0.2   
Target Milestone: 2.0.2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Humberto Ibarra 2016-03-29 21:09:17 UTC
When using the default kernel in yocto-bsp create, the script uses different one. Used x86_64 with default 4.1 kernel, but the script looks for branches from 3.19.

build $ yocto-bsp create test x86_64
Checking basic git connectivity...
Done.

Would you like to use the default (4.1) kernel? (y/n) [default: y]
Do you need a new machine branch for this BSP (the alternative is to re-use an existing branch)? [y/n] [default: y] n
Getting branches from remote repo git://git.yoctoproject.org/linux-yocto-3.19.git...
Please choose a machine branch to base this BSP on: [default: standard/common-pc-64/base]
        1) standard/arm-versatile-926ejs
        2) standard/base
        3) standard/beagleboard
        4) standard/beaglebone
        5) standard/ck
        6) standard/common-pc
        7) standard/common-pc-64/base
        8) standard/common-pc-64/rangeley
        9) standard/edgerouter
        10) standard/fsl-mpc8315e-rdb
        11) standard/mti-malta32
        12) standard/mti-malta64
        13) standard/qemuarm64
        14) standard/qemuppc
Comment 1 Benjamin Esquivel 2016-03-31 18:06:43 UTC
this seems to be only failing for Jethro which should be targeted then for 2.0.2
Comment 2 Humberto Ibarra 2016-04-05 16:13:53 UTC
This is indeed only happening in jethro.

Sent patch

https://lists.yoctoproject.org/pipermail/poky/2016-April/010472.html
Comment 3 Leonardo Sandoval Gonzalez 2016-04-07 16:55:26 UTC
The sent patch is targeted to 2.0.X so moving the milestone