linux/poky.git/meta/lib/oe/sstatesig.py, branch krogoth-next

sstatesig.py: Add a method to "unlock" recipes

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

In order to support workflows using devtool where a user might want to modify tasks that exist in locked-sigs.inc, there must be a way to unlock recipes. This patch adds that support by allowing the user to add recipes to SIGGEN_UNLOCKED_RECIPES. Recipes that exist in that variable will have all their tasks unlocked, as well as any tasks that depend on that recipe. For example if foo->bar->baz, if you unlock baz, it will also unlock bar so that foo can be rebuilt without explicitly specifying bar as being unlocked. [YOCTO #9195] (From OE-Core rev: 8a8fc54d824767a6a94d12a4ace98b0bdbb1aa25) Signed-off-by: Randy Witt Signed-off-by: Richard Purdie

sstatesig.py: Improve the SIGGEN_LOCKEDSIGS_TASKSIG_CHECK message

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

The previous message when signatures didn't match between the metadata and the locked signatures file, the message output was a bit confusing. Now the message should be of the form: The zlib-native:do_install sig is computed to be 53531910a2a7848432da89def942a91a, but the sig is locked to d25ba9035f7ccb308e51bbe1066e8d27 in SIGGEN_LOCKEDSIGS_t-x86-64 which will hopefully be more useful in understanding the problem. [YOCTO #9195] (From OE-Core rev: 49eeabfff8bbea69401db41f7219e29acf47af73) Signed-off-by: Randy Witt 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

sstatesig: Ensure we keep native depends for allarch recipes

2016-03-29T22:20:12+00:00

Without this, do_package_write_rpm doesn't depend on rpm-native which it really should since that is needed to build rpms. [YOCTO #8047] (From OE-Core rev: 3fab4f9920d004fe13fb01434d4c7f3b8bbd7895) Signed-off-by: Richard Purdie

lib/sstatesig: skip shared_workdir when checking locked sigs

2016-03-09T17:00:28+00:00

do_shared_workdir is not a proper sstate task, it always reruns if needed, so special-case it in warnings when checking locked sigs. (From OE-Core rev: 4b08f982a2b15bff9092f60f7957301bb2d2108b) Signed-off-by: Joshua Lock Signed-off-by: Richard Purdie

sstatesig: Handle special case of gcc-source shared-workdir for printdiff

2016-01-11T15:41:47+00:00

Often, bitbake -S printdiff would show that there was a checksum not found which would turn out to be from gcc-source. This is due to it being a shared-workdir recipe. For now, hardcode the special case into the sstatesig code to stop people (including me) puzzling over this. If/as/when we add any other shared workdir recipes, we'll need to rethink this. (From OE-Core rev: f11342f0c838b520828927c9d69f7c17309c1b48) Signed-off-by: Richard Purdie

lib/oe/sstate: Add tasks_resolved handler for virtual/xxx mappings

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

In SIGGEN_EXCLUDERECIPES_ABISAFE and SIGGEN_EXCLUDE_SAFE_RECIPE_DEP we really need to be able to use virtual/xxx namespaces but this currently doesn't work. To make this work, we need to translate them into the resolved providers. After such a hook was added to bitbake, we can add this translation here. (From OE-Core rev: 0a6d0d040ab7f885b667a34f4ddcc775d135c07c) Signed-off-by: Richard Purdie

classes/sstate: break out function to get sstate manifest filename

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

It is useful in a few different contexts to see which files have been written out by an sstate task; break out a function that lets us get the path to the manifest file easily. (From OE-Core rev: 090196dd2d8f4306b34b239e78c39d37cc86034c) Signed-off-by: Paul Eggleton Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

oe.sstatesig: align swspec handling with sstate.bbclass

2015-04-08T09:53:16+00:00

The logic tries to remove the -native suffix from pn to handle this (though it doesn't succeed, as it doesn't assign the new pn to the variable), but we need to do more for the swspec tasks than just not set the extrapath, we also need to change from SSTATE_PKGSPEC to SSTATE_SWSPEC. Alter to correct the spec for these cases, and also add preconfigure to align with the current logic in sstate.bbclass, which includes that task as well in the list of tasks to adjust to use swspec. [YOCTO #7563] (From OE-Core rev: c9105597763be4bf5bc0ec97cc999566d0f10678) Signed-off-by: Christopher Larson Signed-off-by: Richard Purdie

sstatesig: Add ability to filter list of tasks for locked-sigs.inc

2015-02-24T17:41:42+00:00

(From OE-Core rev: ed4287a60b33cb597eb7fa13b3855a528315b3b0) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie