This causes lots of boot issues, and the reason should come from Josh's recent change: commit 1d0757f16beb31551733d9d755d72337ccda9642 Author: Joshua Lock <josh@linux.intel.com> Date: Tue Aug 24 11:32:01 2010 +0100 opkg: use var for state files, not libdir Fixes [BUGID #221] Signed-off-by: Joshua Lock <josh@linux.intel.com> After a quick glimps, some class files still remain using old path, which is the reason for the mess here. I'll go for a quick look whether it can be easily fixed. If not, then leave to Josh who has more knowledge her.
I've sent out a pull request for this bug. Tested on x86 and arm target. 22db36b5dfbd3002d990d512ea33fd3359ef1d94 in http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=tk/master
Thanks Kevin, I merged your fix and also an extra one for meta-toolchain. 8ea7fa6d4c7734da6034d44f8b6d78d2993f1949 opkg: finalize the change to var directory commit 1d0757f16beb31551733d9d755d72337ccda9642 changes opkg run state from /usr/lib/opkg to /var/lib/opkg, which however is incomplete and still many important information is kept under old directory including postinst methods. This makes latest boot into a mess. So finalize this movement to /var here. Fix [BUGID #229] e10703aa5b008e5bd4ba00606e633281759496fe meta-toolchain: update to reflect opkg state directory move
thanks Josh. I didn't note meta-toolchain. :-)
I have verified this bug is fixed now, by checking the boot message of target message. Now postinst methods are indeed invoked.