Bug 5585 - .bbappend does not update rootfs image
Summary: .bbappend does not update rootfs image
Status: VERIFIED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 1.6
Assignee: Richard Purdie
QA Contact: Andra Necula
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-11-21 18:02 UTC by Tom Walsh
Modified: 2014-09-05 12:14 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Done (doc changes complete)

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 Tom Walsh 2013-11-21 18:02:00 UTC 
While using Dora 10.0.0 and following BSP documentation at: http://www.yoctoproject.org/docs/latest/bsp-guide/bsp-guide.html#customizing-a-recipe-for-a-bsp

The rootfs "interfaces" is not updated / replaced with 'bitbake core-image-minimal'.  You have to do a 'bitbake -c clean core-image-minimal ; bitbake core-image-minimal' before the image is updated with that of the .bbappend'ed recipe within the meta-<machine>.

Bitbake seems to work correctly in parsing the bbappend out and will create+build the recipe inside tmp/work tree using the PRINC value.  However, the build does not trigger a proper rebuild of the target image.
Comment 1 Richard Purdie 2013-11-27 21:13:22 UTC 
Tracked the issue down to a problem in the sstate checksums used for images and a bug in sstatesig.py. There is a patch on the mailing list.

There is also a documentation issue, we should drop PRINC from the docs as you don't need it anymore. CC'ing Scott on that.
Comment 3 Andra Necula 2014-09-05 12:05:07 UTC 
Verified on commit a44006262cf3b810ec78b4cccd8076102a7a0f3e
Comment 4 Scott Rifenbark 2014-09-05 12:14:25 UTC 
Hi, 

I thought I better note in here that commit 	d5a0a6b67632c99ea08e2782e8b7e345962470df into poky and 	88a075e6306349e5f8c0d53b5288ef1e64956cd3 into yocto-docs took care of the documentation component for this bug.  This was handled back in March of 2014.  PRINC has been noted as 'deprecated' and the user should rather use a PR Service.

Scott