linux/poky.git/meta/lib, branch yocto-1.7

sdk.py: fix write target sdk manifest failed based on ipk

2014-10-10T15:44:33+00:00

bitbake meta-toolchain ls tmp/deploy/sdk/poky-glibc-x86_64-meta-toolchain-i586-toolchain-1.7.manifest -al ... |-rw-rw-r-- 1 root root 0 Oct 10 15:05 tmp/deploy/sdk/poky-glibc-x86_64- meta-toolchain-i586-toolchain-1.7.manifest ... The manifest is empty, the reason is target's ipk config path is d.getVar('IPKGCONF_TARGET') rather than d.getVar('IPKGCONF_Target') (From OE-Core rev: 81b3cc448f040dcb4c2f2b05983231ac53270663) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie

oeqa/dmesg: Whitelist usbhid failures

2014-10-02T09:58:24+00:00

We fixed these in parselog but not here. This test really can just be deleted now really. (From OE-Core rev: c598dbdbaebf95cc26e95138b4c3fcb15af67a88) Signed-off-by: Richard Purdie

oeqa/parselogs: Ignore qemu usbhid errors

2014-10-01T23:42:44+00:00

These are harmless from the USB pointer device we install, ignore them. (From OE-Core rev: f5bdf41e78ff378fe23d8ba1543917bc64def62f) Signed-off-by: Richard Purdie

deb_packaging: Added support for multilib

2014-09-30T13:33:31+00:00

The Package Manager implementation for deb didn't take a look about multilib enabled variants. Changes are made for generate apt.conf, sources.list and debian repo index Release and Packages files. [YOCTO #1502] (From OE-Core rev: b5fb879b351cc23977f3e441f758101551297566) Signed-off-by: Anibal Limon Signed-off-by: Richard Purdie

rootfs.py: catch inner warn message

2014-09-30T13:10:34+00:00

Package managements (smart/apt-get/opkg-cl) generate some warn messages to stdout, and we need to catch them and output by bb.warn. Here is an example, while invoking smart to attempt install doc packages, if install failed, it generates warn message to stdout. ... |warning: Can't install util-linux-doc-2.24.2-r1@i586: Can't install util-linux-doc-2.24.2-r1@i586: no package provides info ... The fix catches it and outputs: ... |WARNING: log_check: There is a warn message in the logfile |WARNING: log_check: Matched keyword: [warn] |WARNING: log_check: warning: Can't install util-linux-doc-2.24.2-r1@ i586: Can't install util-linux-doc-2.24.2-r1@i586: no package provides info ... (From OE-Core rev: f8d725f49f2be4b854f523a5ee3a5c4357e67e30) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie

oeqa/utils: Added filter to LogResults decorator to enforce custom log level.

2014-09-29T11:12:44+00:00

(From OE-Core rev: 65c97d4abd26f38917cd89b5f50f7299221b2123) Signed-off-by: Lucian Musat Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oeqa/selftest: Added decorators to buildoptions.py

2014-09-22T12:04:23+00:00

(From OE-Core rev: ea393e90055ea13b0c5a6950dbd388e826a66623) Signed-off-by: Lucian Musat Signed-off-by: Richard Purdie

sstatesig: fix overrides behaviour to remove SIGGEN_LOCKEDSIGS_i586

2014-09-17T21:00:26+00:00

Require a sig file which SIGGEN_LOCKEDSIGS_i586 is not null, but the actual SIGGEN_LOCKEDSIGS_i586 is null. Invoking 'bitbake -e' and we got: ... 3935 # $SIGGEN_LOCKEDSIGS_i586 [2 operations] 3936 # set /path/to/locked-sigs.inc:8576 3938 # del data_smart.py:406 [finalize] 3939 # "" ... It was caused by the following commit: ... (Bitbake rev: 899d45b90061eb3cf3e71029072eee42cd80930c) Author: Richard Purdie Date: Tue May 31 23:52:50 2011 +0100 bitbake/data_smart: Change overrides behaviour to remove expanded variables from the datastore ... We add prefix 't-' to type to workaround the overrides behaviour. (From OE-Core rev: f6a39cc957bf85ff43513f0b76afc3b2c9c906b6) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie

sstatesig.py: Replace '_'s with '-'s in SSTATE_LOCKEDSIGS* names.

2014-09-17T21:00:26+00:00

Using underscores in the "types" parts of the variable names can cause unexpected issues with overrides. For example, if you have both SSTATE_LOCKEDSIGS_x86_64 and SSTATE_LOCKEDSIGS_x86_64_i586, and i586 is in OVERRIDES, then you lose all of the contents in SSTATE_LOCKEDSIGS_x86_64 and thus don't get some of the locked sstate. Using '-'s in the variable names instead, eliminates these issues. (From OE-Core rev: 6662c412a949a9f6b602c848e6303b19db7e5272) (From OE-Core rev: 65f558a6f762fb13224091dc22903b58eeb9b392) Signed-off-by: Richard Purdie

sstatesig: Improve the support for locked down sstate cache usage

2014-09-17T21:00:25+00:00

Add code in the sstate hash validation code to ensure it really did install these from sstate since if it didn't should to warn/abort the build. The judgment condition is: 1) If a build is replaced by locked sstate-cache, it will triger a warn/error; 2) If objects are not used from the locked cache, it will triger a warn/error; 3) Use SIGGEN_LOCKEDSIGS_CHECK_LEVEL variable controls whether this is just a warning or a fatal error or nothing to report. [YOCTO #6639] (From OE-Core rev: 305912dce61c4fed0cbf631aa98a9e6f29db88e4) (From OE-Core rev: 1683815695f39d4bad352348913f927ac8a1bcf5) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie