Error: when reparsing

Technical Support
, , , ,
1

Hi,

I was building a custom-linux-image. I succesfully build the image with the
help of bitbake tool.

When rebuilding the same image again, i was experiencing an error.

ERROR: When reparsing .do_install, the basehash value changed from
3c2401cc61fce5eb899de19dbf78862f to 558516a74162944aff656a7d01321b12. The
metadata is not deterministic and this needs to be fixed.

Then i deleted the build/tmp and build/sstate, and again tried to rebuild.
But Now I encountered with an another errors.

Error:
/home/src/oe-core/build/tmp/deploy/ipk/all/nativesdk-packagegroup-sdk-host_1.0-r11_all.ipk Matched in b
manifest-i686-native-sdk-packagegroup-sdk-host.deploy-ipk
please verify which package should provide the above files.
Note: Tasks Summary: Attempted 3172 tasks of which 2449 didn’t need to be rerun and all succeeded.

NOTE: Tasks Summary: Attempted 3172 tasks of which 2449 didn’t need to be
rerun and all succeeded.

I deleted all the files in /deploy/ipk, build/sstate, build/tmp-glibc and
also deploy/sdk/ for building a new image.

Is there any alternative for rebuilding the image without the above errors
and without deleting the file everytime.

2

If it reports all succeeded you are all set and can ignore any other messages really or what exactly is not working for you?

3

Note that we see this issue every now an then too.
So far we did not find a working solution to address the messages which had no bad side effects.

So as Marcel said, ignore those for the moment.

Patches welcome.

4

bump
I know this is an old issue. I’m not sure whether it’s preferred to add a comment 17 months later, or open a new issue. Here’s the comment.

The error message

[…] The metadata is not deterministic and this needs to be fixed.

still comes up occasionally. For example:

ERROR: When reparsing /home/rdepew/workspace/oe-core3/build/…/layers/meta-toradex-demos/recipes-images/images/console-tdx-image.bb.do_image_teziimg, the basehash value changed from 0ae16f95ce746de6014e081aaa10c324 to 3625ef6cf09724d4e796f3b313c1056a. The metadata is not deterministic and this needs to be fixed.

NOT A FIX, BUT A WORKAROUND: Repeat the ‘bitbake’ command a few more times. The error condition appears to be self-healing.

In the example which produced the above error code:

  • The first execution of ‘bitbake’ resulted in 14 of these errors.
  • The second execution of ‘bitbake’ resulted in 3 of these errors.
  • The third execution of ‘bitbake’ resulted in zero errors.
5

We did not make any progress on the issue.

6

Thanks for your Input.

7

@rdepew : that workaround still isn’t foolproof due to the fact that if someone decides to do a “clean” build everytime they have a change in the image, then all the basehash errors would re-emerge.

8

@danny911: Very true. It seems like, with every clean build, the ‘bitbake’ command will need to be repeated multiple times. So the workaround isn’t foolproof, and if you do clean builds frequently, it can get annoying.