[OE-core] [PATCH v1] postinst-intercepts: check tool presence in intercept hooks

Richard Purdie richard.purdie at linuxfoundation.org
Wed Jun 26 21:21:21 UTC 2019


On Wed, 2019-06-26 at 13:33 -0400, Sinan Kaya wrote:
> Here is my investigation:
> 
> The intercepts are executed on QEMU during cross-compilation using
> qemu-wrapper.
> 
> I see that the tools were built for the native architecture but
> of course they do not exist on the target image and I have no
> interest in pulling fonts and such into my image to make bitbake
> happy.
> 
> DEBUG: Collected intercepts:
>   poky/scripts/postinst-intercepts/update_font_cache
>   poky/scripts/postinst-intercepts/update_gio_module_cache
>   poky/scripts/postinst-intercepts/update_gtk_immodules_cache
>   poky/scripts/postinst-intercepts/update_icon_cache
>   poky/scripts/postinst-intercepts/update_pixbuf_cache
>   poky/scripts/postinst-intercepts/update_udev_hwdb
> 
> I also see that other intercepts are doing the same folder/executable
> checks.
> 
> What is so special about these?

Put another way, why aren't lots of people seeing failures due to this?

You're obviously doing something differently to everyone else but we're
having a hard time understanding what, or how we'd trigger the problem
you're seeing. 

We're nervous about fixing problems we don't understand, not least as
it potentially means we have a huge hole in our test matrix. Your
patches shouldn't be necessary as I understand the codebase either.

Cheers,

Richard



More information about the Openembedded-core mailing list