Bug 13127 - changes in bbappend do not trigger a rebuild
Summary: changes in bbappend do not trigger a rebuild
Status: RESOLVED FIXED
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.7 M2
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
: 13151 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-01-07 17:49 UTC by Jin
Modified: 2019-01-28 10:50 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

Note You need to log in before you can comment on or make changes to this bug.
Description Jin 2019-01-07 17:49:15 UTC
We're using poky 2.5.1, bitbake version reports:

bitbake --version
BitBake Build Tool Core version 1.38.0

We have a msmtp_%.bbappend where we modify pkg_postinst_ontarget by appending to it:

pkg_postinst_ontarget_${PN}_append() {
    killall -9 inotifyd || true
}

I am observing that changes in pkg_postinst_ontarget_${PN}_append() are not being picked up in incremental builds, i.e. I can change the line in the ontarget append function and the package is not being rebuilt.

If I cleanall the package and build it again, then my changes are there.

We are using prserv in our setup and for instance, changes in do_install_append() cause a rebuild an a prserv initiated pr bump, but changes in pkg_postinst_ontarget_${PN}_append() seem to be ignored. I can easily and consistently reproduce it in my setup.

It's worth mentioning, that when I run bitbake -e msmtp and look for pkg_postinst_ontarget_msmtp= in the output, then I do see my changes there.
Comment 1 Richard Purdie 2019-01-10 15:29:18 UTC
At a guess pkg_postinst_ontarget needs to be listed in PACKAGEVARS in package.bbclass for this to work properly.
Comment 3 Alexander Kanavin 2019-01-28 10:50:10 UTC
*** Bug 13151 has been marked as a duplicate of this bug. ***