Bug 9195 - extensible sdk: changing the metadata does not produce an error or warning when running devtool build
Summary: extensible sdk: changing the metadata does not produce an error or warning wh...
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.1
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.1 M4
Assignee: Randy Witt
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-03-01 23:32 UTC by Randy Witt
Modified: 2016-04-14 20:10 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 Randy Witt 2016-03-01 23:32:02 UTC 
Since the extensible sdk uses a locked-sigs.inc file, it is expected that tasks shouldn't run that aren't in that file. However, new task sstate can be generated for tasks that don't match a hash in locked-sigs.inc, and no warning or error will be shown. Here is a method to show this:

1. Extract sdk
2. Delete zlib from sstate-cache
3. Modify zlib:do_install
4. Remove tmp
5. bitbake core-image-minimal
6. It rebuilds with no error or warning
Comment 1 Ross Burton 2016-04-14 20:10:58 UTC 
Fixed in oe-core 6b2b5ffdcb8bf885a1c756ea132e9d2c55e13dcd.