linux/poky.git/meta/classes, branch uninative-2.7

rootfs-postcommands: Avoid use of an hard-coded value

2019-10-02T19:22:25+00:00

(From OE-Core rev: 520c6f30cd571166a0d890d86b461f24f7a6998f) Signed-off-by: Alessio Igor Bogani Signed-off-by: Richard Purdie

base: Improve module import error message

2019-10-02T19:22:25+00:00

Turn: ERROR: Unable to parse Var Traceback (most recent call last): File "Var ", line 1, in File "/media/build1/poky/meta/classes/base.bbclass", line 35, in oe_import(d=): for toimport in oe.data.typed_value("OE_IMPORTS", d): > imported = __import__(toimport) inject(toimport.split(".", 1)[0], imported) File "/media/build1/poky/meta/lib/oe/sstatesig.py", line 267, in : >class SignatureGeneratorOEEquivHash(SignatureGeneratorOEBasicHashMixIn, bb.siggen.SignatureGeneratorUniHashMixIn, bb.siggen.SignatureGeneratorBasicHash): name = "OEEquivHash" bb.data_smart.ExpansionError: Failure expanding variable OE_IMPORTED[:=], expression was ${@oe_import(d)} which triggered exception AttributeError: module 'bb.siggen' has no attribute 'SignatureGeneratorUniHashMixIn' into: ERROR: Error importing OE modules: module 'bb.siggen' has no attribute 'SignatureGeneratorUniHashMixIn' which can then trigger a version mismatch error message. (From OE-Core rev: 5b01726d1cf478aba8d1acc73e29f6cab0c9371e) Signed-off-by: Richard Purdie

packagegroup: fix a comment regarding PACKAGE_ARCH

2019-10-02T19:22:25+00:00

packagegroups whose dependencies are affected by MACHINE_FEATURES need to be marked as MACHINE_ARCH *before* inheriting the packagegroup class, not after. This has changed in commit 9c826962ec8f ("packagegroup: Make allarch inherit conditional"), commit 4f3f34deafe4 in poky but the comment here wasn't updated at the time. (From OE-Core rev: 7eae2502936aa36401491cd1e0e5975db96529ae) Signed-off-by: André Draszik Signed-off-by: Richard Purdie

bash-completion: add image feature

2019-10-02T19:22:25+00:00

Create bash-completion-pkgs image feature to load *-bash-completion packages into an image. The packages are created by the bash-completion bbclass but are currently never loaded. (From OE-Core rev: d47c5981877555a5a6b9aeb93ea6f3c1aa97fc44) Signed-off-by: Joe Slater Signed-off-by: Richard Purdie

icecc: Don't use icecc when INHIBIT_DEFAULT_DEPS is set

2019-10-02T19:22:25+00:00

We don't have a compiler, so no icecc. Silences a spew of warnings of the form: do_configure: Cannot use icecc: could not get ICECC_CC or ICECC_CXX (From OE-Core rev: 0315aabeff8e6483b737d0e23d6841f1394ad3c8) Signed-off-by: Douglas Royds Signed-off-by: Richard Purdie

classes/reproducible_build: Create SDE destination

2019-10-02T19:22:25+00:00

Creates the source data epoch file destination directory when restoring from sstate (From OE-Core rev: f5259a62d444dfc221a9ba592dbca35564f794ac) Signed-off-by: Richard Purdie

populate_sdk_ext: Fix for hash equiv

2019-09-30T15:55:21+00:00

Write out the hash equiv cache file into any eSDK so that it doesn't rely on having to call the hash server for the basic data requests. (From OE-Core rev: 05c6842e747261b3350d6325e238429cf8728ca0) Signed-off-by: Richard Purdie

kernel.fitimage.bbclass: remove ramdisk_ctype

2019-09-27T12:02:17+00:00

set in the ramdisk node the compression property always to "none", as U-Boot nowadays since commit: b1307f884a91 ("fit: Support compression for non-kernel components (e.g. FDT)") decompress non kernel components. Setting compression to the used comression algorithm now, will end in fail of your kernel boot with the ramdisk. This issue is fixed since commit: bddd98573465 ("fit: Do not automatically decompress ramdisk images") which now prints a warning in U-Boot, instead of decompressing the ramdisk, but we should setup compression property correct. (From OE-Core rev: f963a51544a9a7b1abbaa87c95b3c0279847d697) Signed-off-by: Heiko Schocher Signed-off-by: Richard Purdie

classes/reproducible_build: Move SDE deploy to another directory

2019-09-27T12:02:16+00:00

The deployment of the source date epoch file had a race condition where any task attempting to read from the file would race with creation of the sstate archive for the do_deploy_source_date_epoch task. The creation of the sstate archive requires moving the directory to a temporary location, then moving it back. This means that the file disappears for a short period of time, which will cause a failure if any other task is running and trying to open the file to get the current source date epoch. The solution is to copy the source date epoch file to a separate directory when deploying so the file never disappears. When the file is restored from sstate, it is moved to the correct location after being extracted. [YOCTO #13501] (From OE-Core rev: ac27d12fe5480e9b8cc93de6a32bf9631c52d7f4) Signed-off-by: Joshua Watt Signed-off-by: Richard Purdie

classes/image-live.bbclass: Don't hardcode cpio.gz

2019-09-27T12:02:16+00:00

There's INITRAMFS_FSTYPES that can be set differently. (From OE-Core rev: 141d02400696020e83df3edcf13021fde139d261) Signed-off-by: Böszörményi Zoltán Signed-off-by: Richard Purdie