Bug 11106 - eSDK generation fails with rm_work
Summary: eSDK generation fails with rm_work
Status: RESOLVED OBSOLETE
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.5 M3
Assignee: Ross Burton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-02-24 14:53 UTC by Ross Burton
Modified: 2018-02-08 17:59 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 Ross Burton 2017-02-24 14:53:26 UTC 
If I build a eSDK with rm_work enabled:

Exception: FileNotFoundError: [Errno 2] No such file or directory: '/data/poky-master/tmp/work/intel_corei7_64-poky-linux/core-image-minimal/1.0-r0/locked-sigs.inc'
ERROR: core-image-minimal-1.0-r0 do_populate_sdk_ext: Function failed: copy_buildsystem	

Because rm_work has gone and deleted the files...
Comment 1 Paul Eggleton 2017-09-12 10:19:41 UTC 
I couldn't immediately reproduce this. Is there something special I need to do?
Comment 2 Paul Eggleton 2018-01-09 23:50:31 UTC 
Setting NEEDINFO - Ross can you help me to reproduce this?
Comment 3 Ross Burton 2018-02-08 17:59:22 UTC 
Can't make it fail now, so lets close this.