Bug 7114

Summary: rm_work for rootfs skipping the RM_WORK_EXCLUDE variable, results in a wic images with empty rootfs
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Toby Flynn <campingandskiing>
Component: deploymentAssignee: Richard Purdie <richard.purdie>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Undecided CC: philip, richard.purdie
Version: 1.8   
Target Milestone: ---   
Hardware: x86   
OS: arm   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Toby Flynn 2015-01-06 14:18:30 UTC 
With version 1.7 adding RM_WORK_EXCLUDE +="image-name"  would leave the rootfs in the work area fully populated and wic would use it to build an image.  After updating to master I began getting empty rootfs images generated by wic.  

I removed the patch 
http://git.openembedded.org/openembedded-core/commit/meta/classes/rm_work.bbclass?id=6bf06d80c2ce03dfdedac5ad8cf42ef8e36b0ecb and then I received fully populated wic images again.

With the patch in place rootfs contents are removed after performing bitbake image-name. The empty rootfs directory is left so wic will succeed in building an image with an empty rootfs and not report an error.
Comment 1 Phlip Balister 2015-01-06 14:44:16 UTC 
This change is also in dizzy now and broke some stuff I had running.
Comment 2 Richard Purdie 2015-01-07 16:22:10 UTC 
diff --git a/meta/classes/rm_work.bbclass b/meta/classes/rm_work.bbclass
index 7b1ec17..e68d02a 100644
--- a/meta/classes/rm_work.bbclass
+++ b/meta/classes/rm_work.bbclass
@@ -110,3 +110,11 @@ rm_work_rootfs () {
 }
 rm_work_rootfs[cleandirs] = "${WORKDIR}/rootfs"
 
+python () {
+    # If the recipe name is in the RM_WORK_EXCLUDE, skip the recipe.
+    excludes = (d.getVar("RM_WORK_EXCLUDE", True) or "").split()
+    pn = d.getVar("PN", True)
+    if pn in excludes:
+        d.delVarFlag('rm_work_rootfs', 'cleandirs')
+        d.delVarFlag('rm_work_populatesdk', 'cleandirs')
+}
Comment 3 Phlip Balister 2015-01-07 21:45:11 UTC 
That patch resolved the problem for me. Can we get this into dizzy ASAP?
Comment 4 Toby Flynn 2015-01-07 21:59:52 UTC 
This patch worked for me. I verified a correct image is generated.