On Wed, 2013-02-20 at 13:57 +0200, Laurentiu Palcu wrote: > Gconf backend does not accept special characters in configuration source > addresses. When populating SDK target sysroot from core-image-sato, for > example, the configuration source address contains "1.3+snapshot" in it > and '+' is an invalid character. Thus, gconftool-2 will fail and the > build will stop at do_rootfs because the log contains the "ERROR" > string. > > Since failing offline will postpone the postinstall execution for > target's first boot, we can silently fail here, so the build can > complete. > > [YOCTO #3893] > > Signed-off-by: Laurentiu Palcu <laurentiu.pa...@intel.com> > --- > meta/classes/gconf.bbclass | 10 ++++++++-- > 1 file changed, 8 insertions(+), 2 deletions(-)
Just to be clear, I think we need to patch gconf to fix this, there is no good reason it shouldn't be handling the + character (unless you've found one I don't know about). Hiding stderr is a recipe for problems in future and we want these postinstalls to run at build time. Cheers, Richard _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
