On 08/10/2017 12:57 PM, Carlos Rafael Giani wrote:
I was surprised that Yocto does not use fuzz factor 0 by default. The
case above demonstrates how this can lead to confusing errors. Or worse,
recipes might even build but then cause subtle runtime errors...
Is there a reason why the default fuzz factor isn't 0? Is it just
because of the large amount of work required to fix all these patches
that won't apply without a fuzz factor?
You have to ask the author of the patch tool, a certain Larry Wall, why
he set the default fuzz to 2. Yocto didn't do this intentionally, it was
just never really noticed that the default is like this, and can lead to
incorrectly applied patches.
We have a couple of bugs to fix it, you are welcome to voice your
Openembedded-core mailing list