On Wed, 8 Jan 2020 at 22:23, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
On Wed, 2020-01-08 at 14:27 +0100, Alexander Kanavin wrote:
> Remove inet-6-.defn-fix-inverted-checks-for-loopback.patch as
> it is difficult to rebase and not clear if still necessary.
>
> Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
> ---
>  ...efn-fix-inverted-checks-for-loopback.patch | 403 ----------------
> --
>  ...{ifupdown_0.8.22.bb => ifupdown_0.8.35.bb} |  11 +-
>  2 files changed, 5 insertions(+), 409 deletions(-)
>  delete mode 100644 meta/recipes-core/ifupdown/files/inet-6-.defn-
> fix-inverted-checks-for-loopback.patch
>  rename meta/recipes-core/ifupdown/{ifupdown_0.8.22.bb =>
> ifupdown_0.8.35.bb} (83%)


http://errors.yoctoproject.org/Errors/Details/305656/

I had a closer look at how and where ifupdown recipe is used, and from what I see it isn't:
every configuration is relying on busybox to provide the same utilities. That's why the failure is seen only in world builds :)

Should we drop the ifupdown recipe?

Alex