Bug 1181

Summary:	rebuilding an image doesn't redeploy the rootfs
Product:	[Build System, Metadata & Runtime] BitBake	Reporter:	Darren Hart <dvhart>
Component:	bitbake	Assignee:	Richard Purdie <richard.purdie>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	major
Priority:	Medium	CC:	poky.bs.watcher, poky.watcher, sgw
Version:	unspecified
Target Milestone:	1.1 M3
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Darren Hart 2011-06-17 15:48:25 UTC

After making changes that add a recipe to an image, cleanall'ing and rebuilding the image doesn't redeploy the rootfs image to tmp/deploy/images:

Make a change to MACHINE_EXTRA_RRECOMMENDS

$ bitbake -c cleanall core-image-sato
$ bitbake core-image-sato

This shows the new package being built, installed, etc. Eventually the do_rootfs of core-image-sato runs, but tmp/deploy/images/core-image-sato-beagleboard.tar.bz2 is not rebuilt.

I've tried cleaning several of the base images and base tasks, nothing I've tried seems to regenerate the rootfs in tmp/deploy/images. My only recourse has been to start a new clean build and wait for it to complete.

Comment 1 Darren Hart 2011-06-20 10:56:24 UTC

The next time I tried this, I didn't have any trouble, rebuilding the core-image-sato recipe was sufficient. I can't explain what I was seeing before though. Marking as NEEDINFO as I try to see if I can reproduce it. If I can't, we'll close as NOTABUG or similar.

Comment 2 Darren Hart 2011-06-20 10:56:39 UTC

Darren trying to reproduce.

Comment 3 Darren Hart 2011-07-12 11:40:33 UTC

I still haven't been able to reproduce. I suggest closing as unreproducible. We can reopen if we hit it again. As far as I can tell, I was working from a broken environment, the wrong shell, or some other PEBKAC situation...

Comment 4 Richard Purdie 2011-08-05 07:55:07 UTC

Closing since can't be reproduced.