Bug 6650 - Ability to produce locked signatures as part of SDK construction
Summary: Ability to produce locked signatures as part of SDK construction
Status: VERIFIED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.7
Hardware: All Multiple
: Medium+ enhancement
Target Milestone: 1.7 M3
Assignee: Randy Witt
QA Contact: Mihail Stanciu
URL:
Whiteboard:
Depends on: 6422
Blocks: 6662
  Show dependency tree
 
Reported: 2014-08-22 14:35 UTC by Paul Eggleton
Modified: 2015-06-08 18:25 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2014-08-22 14:35:37 UTC 
In order to create the new SDK containing a signature-locked copy of the build system we need to generate the locked signatures, but at the moment that can only be done with a separate invocation of bitbake -S; we need this to be callable during do_populate_sdk so that we eliminate the extra step.
Comment 1 Paul Eggleton 2014-09-18 15:31:50 UTC 
This got implemented before the locked signatures code got merged, marking resolved.
Comment 2 Mihail Stanciu 2014-10-09 14:29:44 UTC 
Discussed with Paul and this cannot be directly verified.
Further discussion concluded that when bug 6422 is verified, this once can also be considered verified.
Comment 3 Mihail Stanciu 2014-10-24 13:05:59 UTC 
Bug 6422 has been verified, therefore marking this as verified as well.
Comment 4 Alexandru Georgescu 2014-10-27 06:33:18 UTC 
Mihai, Paul, Randy,
Do we need to create a TC on this M+ feature?