3919 2013-02-21 14:24:59 +0000 Forced rebuilds are ignored for subsequent builds 2013-02-25 17:15:52 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 1.3 All Multiple RESOLVED FIXED Undecided major --- 1 bluelightning bluelightning dvhart poky.bs.watcher poky.watcher ross.burton --- --- --- oldest_to_newest 30005 0 bluelightning 2013-02-21 14:24:59 +0000 If you use the -f or -C options to force the re-execution of a task, the next time bitbake runs the old version of the task's output will be restored from shared state. The cause of this is the stamp deletion process at the end of running a task also deletes the taint file that we use to alter the task signature, so next time the task is called for it has the old value without the taint. This also affects kernel menuconfig since that taints the do_compile task when it finishes. 30011 1 bluelightning 2013-02-21 15:50:35 +0000 Patch sent for review: http://lists.linuxtogo.org/pipermail/bitbake-devel/2013-February/004171.html 30084 2 dvhart 2013-02-25 17:12:40 +0000 I think I'm hitting this on Danny as well. 30085 3 ross.burton 2013-02-25 17:14:33 +0000 Yep, I intend to encourage this to be merged to the 1.16 branch for danny. 30086 4 dvhart 2013-02-25 17:15:43 +0000 Merged to master: commit 406cb9920fad57a23d2139f657c41598eb5087bf Author: Paul Eggleton <paul.eggleton@linux.intel.com> Date: Thu Feb 21 15:23:35 2013 +0000 bitbake: build.py: avoid deleting taint files when writing stamps