Bug 9595

Summary: Extensible sdk: error early if tasks to be ran cannot be provided from sstate
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Randy Witt <randy.e.witt>
Component: coreAssignee: Randy Witt <randy.e.witt>
Status: RESOLVED OBSOLETE QA Contact:
Severity: normal    
Priority: Medium CC: bluelightning, meta.mr.watcher, meta.watcher
Version: 2.1   
Target Milestone: 2.2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Randy Witt 2016-05-05 16:29:22 UTC 
Right now when running the extensible sdk, if an item is not found in locked signatures it will run the task and build it. This behavior is fine for items that have been specifically unlocked.

Currently there is an error/warning you can turn on for a task not being in sstate. However, this runs for all tasks in the task graph, not just the ones that will actually run. So ideally we would expand that to instead only error if the tasks to be ran don't exist in sstate.
Comment 1 Paul Eggleton 2016-05-05 18:43:09 UTC 
At least part of this may be covered under bug 9367.
Comment 2 Randy Witt 2016-10-25 19:57:09 UTC 
This bug is obsolete since BB_SETSCENE_ENFORCE in conjunction with locked signatures should address the issue.