On Tue, 2 Apr 2019 at 00:18, Oleksandr Kravchuk <[email protected]> wrote: > I wonder that as well. > > As someone rather new to the YP, I would sensitively like to learn why, > so I don't waste your time in the future again, because I have not > ignored the warning/error. I have simply not seen one.
This only happens occasionally and we've never managed to get to the bottom of it. Using the current patch (not a fixed one) can you force it to rebuild libcomps: $ bitbake libcomps -C unpack And then mail me the log.do_patch from the work directory? Also, do you have PATCHRESOLVE set? Probably best to check that using bitbake -e just in case you've a site/distro config setting it: $ bitbake -e | grep PATCHRESOLVE= Thanks for all the patches, it's much appreciated. We're deep in feature freeze right now but I'm queueing them up for when master opens for upgrades again. Ross -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
