Open aaronovz1 opened 7 years ago
Does tmp-glibc/work/orion_64-oe-linux/bundle-orion-image-mega/1.0-r0/rootfs/etc/ssl/certs/ae8153b9.1 exist? Is it in tmp-glibc/work/orion_64-oe-linux/bundle-orion-image-mega/1.0-r0/rootfs.tar or is it really missing?
Somehow the tmp-glibc/work/orion_64-oe-linux/bundle-orion-image-mega/1.0-r0/rootfs does not contain etc/ssl/certs/ae8153b9.1 although tmp-glibc/work/orion_64-oe-linux/orion-image-default/1.0-r0/rootfs did.
Which other tasks where running during this build? In particular bundle-orion-image-mega.do_rootfs and bundle-orion-image-mega.do_mega_image are of interest. The latter should have completed before orion-image-default.do_image.
You can do "bitbake -c clean bundle-orion-image-mega" and then re-try.
I messed up some stuff trying to fix it and had to delete tmp so I can't answer the first couple questions unfortunately. I'll check these things when I see the issue again.
As for using the clean command, I had tried that on a number targets, bundle-orion-image-mega, orion-image, orion-image-default, etc. Didn't seem to fix it - although I think in the past sometimes it had resolved it.
Every so often when I make a change to some recipes, add new packages, etc. I get this error from bsdtar about a file "Not found in archive". The file is never the same each time I have seen this problem. Has anyone seen this before? Is there a safe way to resolve this without deleting the entire tmp directory?