linux/poky.git/meta/classes/sstate.bbclass, branch python3

meta: python3 megapatch

2016-05-16T22:32:39+00:00

This needs splutting into smaller units, WIP atm. (From OE-Core rev: 21529228a7dca96a6a1b44ed9380c523efdeeb3e) Signed-off-by: Richard Purdie

meta: Convert to use python3 octal syntax

2016-05-16T22:32:39+00:00

(From OE-Core rev: 2502a4c65b45d02b606cb790d48b7bcf2e066366) Signed-off-by: Richard Purdie

sstatesig.py: Split single locked sigs check into multiple checks

2016-04-09T22:00:43+00:00

Add the SIGGEN_LOCKEDSIGS_TASKSIG_CHECK and SIGGEN_LOCKEDSIGS_SSTATE_EXISTS_CHECK variables to replace SIGGEN_LOCKEDSIGS_CHECK_LEVEL. SIGGEN_LOCKEDSIGS_TASKSIG_CHECK will no control whether there is a warning or error if a task's hash in the locked signature file doesn't match the computed hash from the current metadata. SIGGEN_LOCKEDSIGS_SSTATE_EXISTS_CHECK will control whther there is a warning or error if a task that supports sstate is in the locked signature file, but no sstate exists for the task. Previously you could only have warning/errors for both controlled by SIGGEN_LOCKEDSIGS_CHECK_LEVEL. This was an issue in the extensible sdk, because we know sstate won't exist for certain items in the reverse dependencies list for tasks. However, we still want to error if task signatures don't match. [YOCTO #9195] (From OE-Core rev: 0fe2a5e5ffd01e926d0f3d4c78ad9910296e2d1a) Signed-off-by: Randy Witt Signed-off-by: Richard Purdie

useradd.bbclass: remove user/group created by the package in clean* task

2016-04-06T21:57:25+00:00

At present, if a recipe is built which creates users/groups via useradd.bbclass, those users/groups are not removed from sysroot when the recipe/package is cleaned using clean/cleansstate/cleanall or when a recipe is rebuild and 'unstaged' from the the sysroot. The "userdel_sysroot_sstate()" provides that functionality. [YOCTO #9262] (From OE-Core rev: b5304ce438666a7418746f4ddd32703ae3188089) Signed-off-by: Maxin B. John Signed-off-by: Richard Purdie

sstate: Allow late expansion of NATIVELSBSTRING

2016-03-07T11:55:37+00:00

uninative needs to adjust NATIVELSBSTRING fairly late in the configuration parsing process but the sstate code encodes it into variables. Since this string doesn't vary on a per recipe basis, we defer its expansion until usage time. (From OE-Core rev: fb680ab8b3cf7aba9b579403b1aeb96d30762320) Signed-off-by: Richard Purdie

cml1/sstate: Fix missing getVar parameter

2016-02-19T15:33:02+00:00

(From OE-Core rev: 84065e9b33e6d401e4e50436665838be2d0267ad) Signed-off-by: Richard Purdie

sstate.bbclass: use oe.gpg_sign for gpg signing

2016-02-19T01:01:25+00:00

[YOCTO #9006] (From OE-Core rev: a3916b29c8c3d0b1570c40c0ed3a1a15c43925bb) Signed-off-by: Markus Lehtonen Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

sstate: Add ca-certificates-native to postinst recipes list

2016-02-16T09:04:23+00:00

(From OE-Core rev: a6426479f6348524a904ba28c16c1e3c8793cb08) Signed-off-by: Ming Liu Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

sstate: Ensure populate_lic sstate objects are cleaned

2016-02-10T16:06:24+00:00

do_cleansstate wasn't cleaning do_populate_lic sstate objects in the native/cross case since the wildcard path entry wasn't being cleared at the same time as the path extra prefix. Fix by clearing it at the same time. (From OE-Core rev: af72c507f5e20acf64b7431cee989af9908ef199) Signed-off-by: Richard Purdie

sstate: Fix SSTATE_SWSPEC only used by populate_lic tasks

2016-02-04T23:39:00+00:00

This variable is only used by populate_lic tasks (gcc-source overrides it) and refers to BPN. In recipes like gcc, where there are multiple variants, it is resulting in sstate objects which encode PN (they install into a PN subdir) but the sstate object reflects BPN. This leads to corruption between then and eventually, warnings from image builds like: WARNING: The license listed GPLv3 was not in the licenses collected for recipe gcc WARNING: The license listed GPL-3.0-with-GCC-exception was not in the licenses collected for recipe gcc WARNING: The license listed GPLv3 was not in the licenses collected for recipe gcc WARNING: The license listed NCSA was not in the licenses collected for recipe gcc-sanitizers WARNING: The license listed MIT was not in the licenses collected for recipe gcc-sanitizers WARNING: The license listed GPL-3.0-with-GCC-exception was not in the licenses collected for recipe gcc WARNING: The license listed GPLv3 was not in the licenses collected for recipe gcc WARNING: The license listed NCSA was not in the licenses collected for recipe gcc-sanitizers By referring to PN, as used by license.bbclass, this issue is resolved. (From OE-Core rev: dd4a319efcfa1174ba0f48fd15cb446280c426e4) Signed-off-by: Richard Purdie