linux/poky.git/meta/recipes-extended/images, branch python3

images: zero out the rootfs_extra_space in initramfs images

2016-04-18T15:28:21+00:00

Setting IMAGE_ROOTFS_EXTRA_SPACE impacts the initramfs images, results in an error about INITRAMFS_MAXSIZE. (From OE-Core rev: 3ee82430f3f3eb62cbc949658808d109222e8b24) Signed-off-by: Stephano Cetola Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oeqa/runtime: remove dmesg test

2015-11-16T11:39:30+00:00

This has been obsoleted by parselogs. (From OE-Core rev: 05132fd236835db71d3e763b4d6ce01fcf14741a) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

recipes-extended: remove duplicate recipe and .wks

2015-10-01T06:43:33+00:00

Removed wic-image-minimal.bb and wic-image-minimal.wks as they're also present in meta-selftest/recipes-test/images/ (From OE-Core rev: 5a52eaf938c75dccf10723979e97523026ecae44) Signed-off-by: Ed Bartosh Signed-off-by: Richard Purdie

wic-image-minimal: add wic image recipe and .wks

2015-09-12T21:48:25+00:00

Added example of recipe and .wks file to create partitioned image. This image is using quite complex partitioning scheme. It uses its own rootfs to populate two partitions in two different ways. It also uses core-image-minimal rootfs to populate another partition. This is how wic reports about artifacts used to create this image: ROOTFS_DIR: tmp/work/qemux86_64-poky-linux/wic-image-minimal/1.0-r0/rootfs ROOTFS_DIR["/core"]: tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/rootfs ROOTFS_DIR["/backup"]: tmp/work/qemux86_64-poky-linux/wic-image-minimal/1.0-r0/rootfs BOOTIMG_DIR: tmp/sysroots/qemux86-64/usr/share KERNEL_DIR: tmp/deploy/images/qemux86-64 NATIVE_SYSROOT: tmp/sysroots/x86_64-linux (From OE-Core rev: 6c33bad0284a2958c45e007e76d615354269bc9d) Signed-off-by: Ed Bartosh Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

core-image-lsb-sdk: use kernel-devsrc to ensure kernel module builds work

2015-07-20T09:40:42+00:00

With the move of the kernel source to the kernel-devsrc, we need this package to ensure the kernel module sanity tests made on core-image-lsb-sdk continue to pass. Therefore update the name of the package included in the image. (From OE-Core rev: b283b82ec59a2137cf717811172765848fa813fa) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

core-image-kernel-dev: Define a correct subset of TEST_SUITES to run for this image

2015-07-07T23:01:20+00:00

Since this image can be built with both poky and poky-lsb, ensure the correct tests are run in both cases, the auto detection does not quite work right in the poky-lsb case since not all the Posix cmdline utilites are added. Add connman and connman test for network sanity (From OE-Core rev: 8df57b4b1a110dcbaab9652795fe5c0d86019554) Signed-off-by: Saul Wold Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

kernel-dev: install all modules by default

2015-02-08T08:00:29+00:00

When doing kernel development testing, we want all the modules that were built to be installed on the target. (From OE-Core rev: 440b827c7953c59a85e3a93b88953cd33a530a07) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

images: introduce core-image-kernel-dev

2014-12-21T12:37:53+00:00

When building a new kernel, or testing and update to the kernel there are a set of packages that are sensitive to APIs, build system and other changes associated with the kernel. After building this recipe, we can be reasonably sure that a new kernel package and coupled userspace have been built, installed and tested via a single image. (From OE-Core rev: 6c22c0e7e7bb392df6d04864f56d66d3a2c1e32b) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

core-image-testmaster.bb: add bzip2 to image

2014-06-13T11:52:20+00:00

YB: #6375 Some test image fstypes require bzip2 decompression. (From OE-Core rev: 7b81fce3a80f7a1b94015a1da95d2349dac577ab) Signed-off-by: Corneliu Stoicescu Signed-off-by: Richard Purdie

core-image-lsb: enforce pam as a needed distro feature

2014-04-01T22:37:01+00:00

core-image-lsb only gave a warning: "WARNING: Building libpam but 'pam' isn't in DISTRO_FEATURES, PAM won't work correctly" when the proper DISTRO was not set for it. default choice would be DISTRO = "poky-lsb", but not necessarily, depending on each custom distro. This fix will enforce the proper usage of pam as a distro feature for core-image-lsb by giving an error instead of just a warning. Fixes [YOCTO #6073] (From OE-Core rev: f7cd6b383f50ebc3000a9d9db8be719ab5b3c0bb) Signed-off-by: Cristian Iorga Signed-off-by: Richard Purdie