Bug 6502

Summary: Image does not get rebuild after changes in image recipe
Product: [Build System, Metadata & Runtime] BitBake Reporter: Volker <lists.volker>
Component: bitbakeAssignee: Roxana Ciobanu <roxana.ciobanu>
Status: RESOLVED FIXED QA Contact:
Severity: minor    
Priority: Medium CC: bluelightning, poky.bs.watcher, poky.watcher, roxana.ciobanu
Version: 1.6.1   
Target Milestone: 1.7   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Volker 2014-07-02 22:53:23 UTC
I had the following in my image recipe
----
set_root_pwd() {                                                                
    # we know we have /etc/shadows because we install openssh
    sed -i 's|^root:[^:]*:|root:XXXXXXXX:|' \
        ${IMAGE_ROOTFS}/etc/shadow
}
# execute function on image creation
ROOTFS_POSTPROCESS_COMMAND += "set_root_pwd;
----
then I run bitbake to set the password and it worked. So I have a current image.

Now I disabled the function by commenting out the one line that actually executes it.
---
#ROOTFS_POSTPROCESS_COMMAND += "set_root_pwd;
---

If I try now to build the image again it wont build
---
NOTE: Tasks Summary: Attempted 2655 tasks of which 2655 didn't need to be rerun and all succeeded.
---

I would have assumed that every change would rebuild the changed component. This does not seem to be the case with the image recipe.



Some more details:

Base of my image recipe:
----
IMAGE_INSTALL = "packagegroup-core-boot ${ROOTFS_PKGMANAGE_BOOTSTRAP} ${CORE_IMAGE_EXTRA_INSTALL}"
inherit core-image                                                              
[other options skipped]
----

My distro.conf contains the following line. This is not relevant if you modify the set_root_pwd() to run some other commands. If you don't modify it, you need th ssh-serveropenssh image feature.
---
IMAGE_FEATURES = "read-only-rootfs ssh-serveropenssh package-management"
---
Comment 1 Magnus Olsson 2015-01-27 10:48:51 UTC
*** Bug 7024 has been marked as a duplicate of this bug. ***