linux/poky.git/bitbake/lib/bb, branch dizzy-12.0.1

bitbake: fetch2/git: Allow other namespaces than refs/heads to be searched.

2015-01-06T14:15:48+00:00

This makes it possble to fetch Gerrit review references which are normally stored under refs/changes. Please disregard previous patch with the same topic. (Bitbake rev: ab8cbf2a71750f5ea36e218036b050857301607b) Signed-off-by: Fredrik Svensson Signed-off-by: Richard Purdie

bitbake: bitbake-worker: exit normally when SIGHUP

2014-12-31T10:10:22+00:00

Fixed: 1) Run "bitbake recipe" in the terminal 2) Close the terminal while building 3) $ ps aux | grep bitbake-worker There will be many processes, and they will keep the resources (e.g., memory), and won't exit unless kill or kill -9. (Bitbake rev: 72536d4e0cc3379001b730950afa012f7a96a79b) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: event: fix resetting class handlers object

2014-12-31T10:10:22+00:00

If you don't explicitly specify to use a global variable when doing an assignment, you will be setting a local variable instead, which means this function wasn't working at all. It explains some odd behaviour we have seen in the layer index where event handlers were sometimes bleeding into other contexts where they should not have been. (Bitbake rev: f12c738d3dc1f0fd105d457385511440024bffab) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: data: Handle BASH_FUNC shellshock implication

2014-12-31T10:10:22+00:00

The shellshock patches changed the way bash functions are exported. Unfortunately different distros used slightly different formats, Fedora went with BASH_FUNC_XXX()=() { echo foo; } and Ubuntu went with BASH_FUNC_foo%%=() { echo foo; }. The former causes errors in dealing with out output from emit_env, the functions are not exported in either case any more. This patch handles things so the functions work as expected in either case. [YOCTO #6880] (Bitbake rev: 4d4baf20487271aa83bd9f1a778e4ea9af6f6681) Signed-off-by: Richard Purdie

bitbake: runqueue: Fix 100% cpu use after keyboard interrupt

2014-12-31T10:10:21+00:00

After Ctrl+C is pressed to interrupt bitbake, it loops continually, running at 100% cpu. This patch selects on the correct file descriptors resolving the excess cpu usage. (Bitbake rev: dca5d82830ef2838439e5272da9dac1f28954cf1) Signed-off-by: Richard Purdie

bitbake: buildinfohelper: Make sure we use the orm defined value for loglevel

2014-12-31T10:10:21+00:00

We need to consistently use LogMessage.INFO/WARNING/ERROR to make sure toaster knows how to categories these rather than passing in the "raw" loglevel value which in best case comes from python logging but worst case any value. [YOCTO 6885] (Bitbake rev: 926235aad806232bc73e33d6dd8955dd26562e6b) Signed-off-by: Michael Wood Signed-off-by: Richard Purdie

bitbake: siggen: Fix shared work checksum mismatch/rebuild issues

2014-11-20T17:24:48+00:00

Similar to the last shared work task signature bug, we've found another one. Looking at the improved output of diffsigs in this case: runtaskdeps changed from [ 'autoconf_2.69.bb.do_populate_sysroot:virtual:native', 'gnu-config_20120814.bb.do_populate_sysroot:virtual:native', 'libgcc-initial_4.9.bb.do_patch:virtual:nativesdk' ] to [ 'autoconf_2.69.bb.do_populate_sysroot:virtual:native', 'gcc-crosssdk-initial_4.9.bb.do_patch', 'gnu-config_20120814.bb.do_populate_sysroot:virtual:native' ] so we can get a different task hash since libgcc sorts before gnu-config and gcc sorts after it. We could do with a way of fixing this, the best I can come up with is to include a single parent directory. Since recipes are never at the top of any metadata trees I've seen, this should suffice for now. I'm planning to burn the concept of shared work within bitbake and do something at the metadata level in the 1.8 timeframe as its just too fragile as things stand and hard to fix well. (Bitbake rev: fc7ebf3835a206a5daafd4e1b73bac2549714ad3) Signed-off-by: Richard Purdie

bitbake: data_smart.py: fix variable splitting at _remove mechanism

2014-11-19T10:46:41+00:00

If we split variables only at whitespaces, a slipped in tab will render a value unremovable. (Bitbake rev: 0da22ba3e930fbb060b31fc423fd3333ca8843a0) Signed-off-by: Stefan Müller-Klieser Signed-off-by: Richard Purdie

bitbake: fetcher: fix getVar call due to incorrect argument datatype

2014-10-11T07:11:03+00:00

(Bitbake rev: 2ac33aac3446cb12227f1b8daa5f27f417c9bb9e) Signed-off-by: Alejandro Hernandez Signed-off-by: Richard Purdie

bitbake: fetcher: fix BB_STRICT_CHECKSUM datatype check

2014-10-06T15:09:53+00:00

Forcing strict to be a string, to avoid problems when performing comparisons [YOCTO #6762] (Bitbake rev: b8ed2098bdea2afd93ab4e3e1b834f3a31cb60de) Signed-off-by: Alejandro Hernandez Signed-off-by: Richard Purdie