On Thu, 2011-12-22 at 10:10 +0100, Martin Jansa wrote: > See http://bugzilla.pokylinux.org/show_bug.cgi?id=1711 > but it's still broken in some cases (on my buildhost 3 from 5 machines > are broken, 2 are working after last opkg changes).
Do we have any more details on what is broken or how this is happening? I'm at a loss as to how to help with this. > Good test is to enable testlab and run this in your deploy/images directory > find . ! -type l -name \*tar.gz`; do > echo $i; > tar -tvf $i | grep dbus-daemon-launch; > tar --numeric-owner -tvf $i | grep dbus-daemon-launch; > tar xzvpf $i ./etc/group; > grep messagebus ./etc/group; > done | tee -a image.test > > And working image needs to have not only messagebus as owner but also > matching GID in 2nd line and last line from packaged /etc/group. With > latest opkg fixes it seems to work, but only if there is messagebus in > packaged /etc/group at all, reported here: > http://lists.linuxtogo.org/pipermail/openembedded-core/2011-December/014619.html > but probably got lost in other issues with new opkg, like this one > http://lists.linuxtogo.org/pipermail/openembedded-core/2011-December/014654.html > (if D is not needed to be set from opkg then why was offlineroot_varname.patch > added in first place? and I have updated this after > offlineroot_varname.patch removal and new version is in shr branch) I added offlineroot_varname at a point when the export D in rootfs_ipk.bbclass was later. In the final version I moved it and the other exports earlier to fix different problems. The patch still looked like a good idea at that point. When a problem appeared with the patch I decided just to drop it. We should probably continue to export PKG_ROOT for compatibility and maybe export D in addition to that. Cheers, Richard _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
