linux/poky.git/meta/lib, branch 2.5_M2

rootfs.py: change the notice about deferring scripts to first boot from warning to a note

2018-01-30T11:50:12+00:00

Now that the first boot deferral needs to be requested explicitly, it's not really something to be concerned about. (From OE-Core rev: 19f3f4c60060ff5ed3c1c9871e18fcd4d128c5a3) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

meta/lib/oe/package_manager.py: deprecate 'exit 1' as a way to defer to first boot

2018-01-30T11:50:12+00:00

'exit 1' is not optimal for two reasons: 1) Code is hard to read; it is not obvious that it means 'defer what follows to first boot'. 2) Worse, this hides actual errors in the scriptlets; there is no difference between scriptlet failing because it's intended to be run on target and scriptlet failing because there's a bug or a regression somewhere. The new, supported way is to place the code that has to run on target into pkg_postinst_ontarget(), or, if a more fine-tuned control is required, call 'postinst-intercepts defer_to_first_boot' from pkg_postinst() to explicitly request deferral to first boot. (From OE-Core rev: d12cf56e9ff2a4f13dfbef9290ea5647b52b3f6d) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

meta/lib/oe/rootfs.py: do not execute defer_to_first_boot when processing postinst_intercept hooks

2018-01-30T11:50:12+00:00

That hook is empty, and doesn't need to be executed; it merely indicates that packages that have used it are requesting to defer their postinst scripts to first boot unconditionally. (From OE-Core rev: 939f7f1a06cd2db05aeb5e75a66322314e10aa6d) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

meta/lib/oe/rootfs.py: separate first boot deferral logic into a separate function

2018-01-30T11:50:12+00:00

(From OE-Core rev: 4612291411ad788df88d5fc6dde98ff53fd91002) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

oeqa/runtime: add gobject-introspection test

2018-01-29T10:31:58+00:00

(From OE-Core rev: 497a95b576e19e39e20ac280d0db24f51b7c9679) (From OE-Core rev: 7fe336e34bbdc16a28f95ce6ec043943f8033002) Signed-off-by: Richard Purdie

imagefeatures: disable f2fs from test_image_features by default

2018-01-23T23:43:46+00:00

Since the primary f2fs utilities are provided by the meta-openembedded meta-filesystems layer, we disable the testing of that functionality here. (From OE-Core rev: f691ed2572e54fa2af04c1569746c36ce04463ee) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

buildhistory_analysis: colourise more output

2018-01-23T23:43:45+00:00

(From OE-Core rev: e0f2c84e5ee6c4e5a56e485010647ca698d010bf) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

lib/oe/package_manager/sdk: Ensure do_populate_sdk_ext and do_populate_sdk repos don't conflict

2018-01-22T10:39:10+00:00

The repository indexes updated during do_populate_sdk_ext and do_populate_sdk can conflcit. Add the missing lockfile calls for deb/ipk and in the rpm case, ensure different directories are used for the index for the two sdk cases. (From OE-Core rev: 5e5569c962c9ebc898eeb5044214e95117b190e1) Signed-off-by: Richard Purdie

buildhistory-diff: add support for colourising the output

2018-01-18T12:50:37+00:00

Colour value removes in red and additions in green, making it easier to scan the output for relevant changes. This adds a --colour option to specify whether colouring should be on, off, or detected. The default is detected, and depends on whether stdout is a TTY (same behaviour as git). (From OE-Core rev: 4208f1546c92f069e432d1865269ce539db8cea7) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

selftest/cases/devtool.py: fix workspace layer checking

2018-01-14T09:11:57+00:00

Fixed: $ oe-selftest -r devtool.DevtoolTests.test_create_workspace [snip] 2017-12-20 18:28:59,404 - oe-selftest - INFO - Traceback (most recent call last): File "/workspace2/lyang1/poky/meta/lib/oeqa/core/decorator/__init__.py", line 32, in wrapped_f return func(*args, **kwargs) File "/workspace2/lyang1/poky/meta/lib/oeqa/selftest/cases/devtool.py", line 177, in test_create_workspace self.assertTrue('/workspace' not in result.output, 'This test cannot be run with a workspace layer in bblayers.conf') AssertionError: False is not true : This test cannot be run with a workspace layer in bblayers.conf [snip] $ bitbake-layers show-layers NOTE: Starting bitbake server... layer path priority ========================================================================== meta /workspace2/lyang1/poky/meta 5 meta-poky /workspace2/lyang1/poky/meta-poky 5 meta-yocto-bsp /workspace2/lyang1/poky/meta-yocto-bsp 5 meta-selftest /workspace2/lyang1/poky/meta-selftest 5 There is no workspace layer, but I'm in /workspace2, this patch can fix the problem. [YOCTO #12442] (From OE-Core rev: 695b234ea4f034d428f8cffacceabc2b8f00bc74) Signed-off-by: Robert Yang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie