Re: [yocto] Find the cause of a hash mismatch

On 10/17/25 22:19, Jörg Sommer via lists.yoctoproject.org wrote:
> Hello,
>
> I have the problem that Bitbake tells me

<snip>

> They all end with
>
>     Hash for task dependency pseudo/pseudo_git.bb:do_populate_sysroot:virtual:native changed from f6aab8910c7c8c0ab7b4e3ce8cd37280e2ba17bb43899cba137d0d82a16b8dd1 to 9e3aa528d1736c6f23ce8ceb6cf181af447cec7da91859f15e216517516c5271
>     Unable to find matching sigdata for pseudo/pseudo_git.bb:do_populate_sysroot:virtual:native with hashes f6aab8910c7c8c0ab7b4e3ce8cd37280e2ba17bb43899cba137d0d82a16b8dd1 or 9e3aa528d1736c6f23ce8ceb6cf181af447cec7da91859f15e216517516c5271
>
> When I run bitbake-diffsigs I get the same:
>
> + bitbake-diffsigs -t hcpu-image do_rootfs

<snip>

> <>
> How can I track down the cause of the hash mismatch? Any help is
> appreciated, because this problem persists and it drives my crazy.
>
>

If it changes every run, you could try diffing it manually:

bitbake -e pseudo-native > run1
bitbake -e pseudo-native > run2
diff -Naur ./run1 ./run2

Does it give anything that makes sense?