[OE-core] Source deployment conflict when building multiple machines

[Mats Kärrman]

Hi,

Porting an old project from OE-Classic to OE-Core (Dora / distroless) I have run into another issue.

When building for machine aaa everything is fine but when I then try to build the same image for machine bbb (in same context, no intermediate cleaning) there is a conflict while deploying sources. The reason seems to be that the machine is not considered, just the CPU arch (sub directories of deploy/sources are allarch-oe-linux, powerpc-oe-linux, x86_64-linux).

When building for bbb a number of messages like this appear (all for machine specific packages):

"""
WARNING: The recipe shadow-securetty is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
   /home/makr/projects/upgrade_to_oe-core/oe/build/tmp-eglibc/deploy/sources/powerpc-oe-linux/MIT/shadow-securetty-4.1.4.3-r2/shadow-securetty-4.1.4.3-r2.showdata.dump
   Matched in manifest-aaa-shadow-securetty.dumpdata_create_diff_gz
   /home/makr/projects/upgrade_to_oe-core/oe/build/tmp-eglibc/deploy/sources/powerpc-oe-linux/MIT/shadow-securetty-4.1.4.3-r2/shadow-securetty-4.1.4.3-r2.diff.gz
   Matched in manifest-aaa-shadow-securetty.dumpdata_create_diff_gz
Please verify which package should provide the above files.
"""

Is this as expected? Should I do something differently?

Best Regards,
Mats