Bisect points at the commit that introduced the hard pseudo abort:

84e0642ed6aba422583871fc153bbd94380074de is the first bad commit
commit 84e0642ed6aba422583871fc153bbd94380074de
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Tue Sep 29 17:57:38 2020 +0100

pseudo: Abort on mismatch patch

Rather than doing what turns out to be a rather dangerous "fixup" if
we see a file with a different path but the same inode as another file
we've previously seen, throw and abort. Direct the user to a wiki page
where we can maintain information about what this error means.

(From OE-Core rev: 2db491d97da08d44ebd257f98489550a82a7935c)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

:040000 040000 265627b814038c0cc19248bbb885ab7536202e1c acfc4fbeb04a887f2ceeaa029a63a4dd82f7767d M meta
bisect run success

/MR

On Sun, Dec 27, 2020 at 8:43 PM matthias.rampke via lists.yoctoproject.org <matthias.rampke=googlemail.com@lists.yoctoproject.org> wrote:

One more thing: I tried reverting the linux-libc-headers version change (57d5f4ad410d4e9d55bdd9734bf5ab8fa6667a53) and that fails in the same way, so it's not that.

I also realized that the yocto-3.2 tag does not include the 3.2.1 updates; however the same issue happens on 3.2.1 as well.

I will try to bisect this but it seems like it will take a long time since I need to wipe the tmp directory at every step.

/MR