linux-yocto: sync meta and LINUX_VERSION

Richard/Saul,

When doing some clean build testing on my latest changes (given that I'm a bit paranoid), I noticed the kernel config audit throwing some warnings (unset values, etc).

The root cause is that when the config fragments are processed they are assembled into a file with the version string from the kernel tree (which was at v3.0) while the recipe tells the audit to check against 3.0.x. Which means nothing is checked.

The fix is simple, I've bumped the internal version to 3.0.3 and pushed it out. The audits are now clean.

.. and this time, I'm nearly sure I pushed these to the proper branch and generated a pull against it.

The following changes since commit 9ca6806de9d9df9d901774c1b23a14f28f10a844:

docuementation/poky-ref-manual/ref-structure.xml: Changed SRCDATE reference (2011-08-24 19:59:55 -0700)

are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel-oe
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel-oe

Bruce Ashfield (1):
linux-yocto: update meta SRCREV to sync version strings

 meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb |    4 ++--
 meta/recipes-kernel/linux/linux-yocto_3.0.bb    |    2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

1.7.4.1

During the update of the bitbake recipe's string to 3.0.3 the internal version marker in the kernel stayed at v3.0. This meant that kernel configuration auditing the constructed file couldn't be found and audit warnings were thrown. This syncs all the recipes and get back to clean configurations.

---
 meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb |    4 ++--
 meta/recipes-kernel/linux/linux-yocto_3.0.bb    |    2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

index 61210de..16daddf 100644
@@ -11,12 +11,12 @@ KMACHINE_qemumips = "mti-malta32-be"
 KBRANCH = "yocto/standard/preempt-rt/base"
 KBRANCH_qemuppc = "yocto/standard/preempt-rt/qemu-ppc32"
 
-LINUX_VERSION ?= "3.0"
+LINUX_VERSION ?= "3.0.3"
 LINUX_KERNEL_TYPE = "preempt-rt"
 
 SRCREV_machine ?= "67ce0924042a2faa12b71ac3e92175c789c32af6"
 SRCREV_machine_qemuppc ?= "839638f4efda0c70c6f491161ab2c042f5bc3e66"
-SRCREV_meta ?= "13dbce30d6a647228bf5a9483a9b9c2da1514f78"
+SRCREV_meta ?= "5b535279e61197cb194bb2dfceb8b7a04128387c"
 
 PR = "r0"
 PV = "${LINUX_VERSION}+git${SRCPV}"

index a5e208b..e39be0d 100644
@@ -18,7 +18,7 @@ SRCREV_machine_qemuppc ?= "c0da1d35dee9fb63ba6bfc7907a77b0feb89766e"
 SRCREV_machine_qemux86 ?= "8b51ddba0f85a6bb8e105b37a9ac03fb58b9de20"
 SRCREV_machine_qemux86-64 ?= "965dd365cf3652347960f7145ac188c86c323070"
 SRCREV_machine ?= "49d93fb0c9e1645ba0bb8951be23e56ea227a5bd"
-SRCREV_meta ?= "13dbce30d6a647228bf5a9483a9b9c2da1514f78"
+SRCREV_meta ?= "5b535279e61197cb194bb2dfceb8b7a04128387c"
 
 PR = "r1"
 PV = "${LINUX_VERSION}+git${SRCPV}"

1.7.4.1

Merged to master, thanks.

Richard

It looks like the bitbake support 'hg' fetcher, but when building custom package, it said need "mercurial-native", but there is no "mercurial" package in recipes-devtools, of cause, I installed mercurial on host pc.

Does anyone can confirm this problem???

Yi Qingliang
倪庆亮

Insigma

You can add:

ASSUME_PROVIDED += "mercurial-native"

to local.conf to show you have installed mercurial and that bitbake should use it.

Cheers,

Richard