I tried adding INHERIT += "create-spdx" to poky.conf and running it on the autobuilder. There were a surprising number of failures: world builds with multilib enabled: https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/6811 https://autobuilder.yoctoproject.org/typhoon/#/builders/108/builds/4350 ERROR: Task /home/pokybuild/yocto-worker/qemux86-world/build/meta/recipes-core/meta/meta-world-pkgdata.bb:do_create_spdx has circular dependency on virtual:multilib:lib32:/home/pokybuild/yocto-worker/qemux86-world/build/meta/recipes-core/meta/meta-world-pkgdata.bb:do_create_spdx ERROR: Command execution failed: 1 meta-aws: https://autobuilder.yoctoproject.org/typhoon/#/builders/122/builds/2571/steps/13/logs/stdio ERROR: automake-native-1.16.5-r0 do_create_spdx: Error executing a python function in exec_func_python() autogenerated: Exception: FileNotFoundError: [Errno 2] No such file or directory: '/home/pokybuild/yocto-worker/meta-aws/build/build/tmp/deploy/spdx/qemux86-64/recipes/recipe-m4-native.spdx.json' buildtools tarball: https://autobuilder.yoctoproject.org/typhoon/#/builders/20/builds/7301/steps/14/logs/stdio ERROR: nativesdk-libgcc-initial-12.2.0-r0 do_create_spdx: The recipe nativesdk-libgcc-initial is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/pokybuild/yocto-worker/buildtools/build/build/tmp/deploy/spdx/qemux86-64/recipes/recipe-nativesdk-libgcc-initial.spdx.json (matched in manifest-x86_64_linux-nativesdk-libgcc-initial.create_spdx) Please verify which recipe should provide the above files. The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_ALLOW_OVERLAP_FILES may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above. ERROR: nativesdk-libgcc-initial-12.2.0-r0 do_create_spdx: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases. ERROR: Logfile of failure stored in: /home/pokybuild/yocto-worker/buildtools/build/build/tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-qemuwrapper-cross/1.0-r0/temp/log.do_create_spdx.326567 NOTE: recipe nativesdk-qemuwrapper-cross-1.0-r0: task do_create_spdx: Failed ERROR: Logfile of failure stored in: /home/pokybuild/yocto-worker/buildtools/build/build/tmp/work/i686-nativesdk-pokysdk-linux/uninative-tarball/1.0-r0/temp/log.do_create_spdx.326566 NOTE: recipe uninative-tarball-1.0-r0: task do_create_spdx: Failed ERROR: Task (/home/pokybuild/yocto-worker/buildtools/build/meta/recipes-core/meta/uninative-tarball.bb:do_create_spdx) failed with exit code '1' ERROR: Task (virtual:nativesdk:/home/pokybuild/yocto-worker/buildtools/build/meta/recipes-devtools/qemu/qemuwrapper-cross_1.0.bb:do_create_spdx) failed with exit code '1' NOTE: recipe nativesdk-linux-libc-headers-6.1-r0: task do_unpack: Succeeded NOTE: Running task 1262 of 1373 (virtual:nativesdk:/home/pokybuild/yocto-worker/buildtools/build/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_6.1.bb:do_create_spdx) NOTE: recipe nativesdk-linux-libc-headers-6.1-r0: task do_create_spdx: Started ERROR: nativesdk-linux-libc-headers-6.1-r0 do_create_spdx: The recipe nativesdk-linux-libc-headers is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/pokybuild/yocto-worker/buildtools/build/build/tmp/deploy/spdx/qemux86-64/packages/nativesdk-linux-libc-headers-dev.spdx.json (matched in manifest-x86_64_linux-nativesdk-linux-libc-headers.create_spdx) /home/pokybuild/yocto-worker/buildtools/build/build/tmp/deploy/spdx/qemux86-64/packages/nativesdk-linux-libc-headers-dbg.spdx.json (matched in manifest-x86_64_linux-nativesdk-linux-libc-headers.create_spdx) /home/pokybuild/yocto-worker/buildtools/build/build/tmp/deploy/spdx/qemux86-64/recipes/recipe-nativesdk-linux-libc-headers.spdx.json (matched in manifest-x86_64_linux-nativesdk-linux-libc-headers.create_spdx) Please verify which recipe should provide the above files.
I had a look at the nativesdk spdx document conflicts. There were two differences: cat tmp/deploy/spdx/qemux86-64/recipes/recipe-nativesdk-libgcc-initial.spdx.json | python3 -m json.tool > 1 cat tmp/work/i686-nativesdk-pokysdk-linux/nativesdk-libgcc-initial/12.2.0-r0/spdx/deploy/recipes/recipe-nativesdk-libgcc-initial.spdx.json | python3 -m json.tool > 2 The creation timestamp: "created": "2023-04-06T10:42:12Z" vs "created": "2023-04-06T08:57:46Z" and the crosssdk dependencies are different: "externalDocumentId": "DocumentRef-dependency-recipe-binutils-crosssdk-i686-pokysdk-linux", "spdxDocument": "http://spdx.org/spdxdoc/recipe-binutils-crosssdk-i686-pokysdk-linux-57774119-cb60-5756-b5a3-e9f14646ed16" "externalDocumentId": "DocumentRef-dependency-recipe-binutils-crosssdk-x86_64-pokysdk-linux", "spdxDocument": "http://spdx.org/spdxdoc/recipe-binutils-crosssdk-x86_64-pokysdk-linux-29d4cb2f-923c-5529-9b92-fc13647f4afc" "relationshipType": "BUILD_DEPENDENCY_OF", "spdxElementId": "DocumentRef-dependency-recipe-binutils-crosssdk-i686-pokysdk-linux:SPDXRef-Recipe-binutils-crosssdk-i686-pokysdk-linux" "relationshipType": "BUILD_DEPENDENCY_OF", "spdxElementId": "DocumentRef-dependency-recipe-binutils-crosssdk-x86_64-pokysdk-linux:SPDXRef-Recipe-binutils-crosssdk-x86_64-pokysdk-linux"
David, Can you work on this ASAP? Joshua is not really available for a few weeks.
https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/2645/steps/12/logs/stdio ERROR: python3-cryptography-39.0.2-r0 do_create_spdx: Error executing a python function in exec_func_python() autogenerated: Exception: FileNotFoundError: [Errno 2] No such file or directory: '/home/pokybuild/yocto-worker/reproducible/build/build-st/reproducibleA/tmp/deploy/spdx/qemux86-64/recipes/recipe-python3-pycparser-native.spdx.json'
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/5046/steps/14/logs/stdio https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/5016/steps/15/logs/stdio ERROR: ccache-native-4.7.4-r0 do_create_spdx: Error executing a python function in exec_func_python() autogenerated: Exception: FileNotFoundError: [Errno 2] No such file or directory: '/home/pokybuild/yocto-worker/oe-selftest-ubuntu/build/build-st-2913083/tmp/deploy/spdx/qemux86-64/recipes/recipe-autoconf-native.spdx.json' https://autobuilder.yoctoproject.org/typhoon/#/builders/127/builds/1208/steps/14/logs/stdio ERROR: libgfortran-12.2.0-r0 do_create_spdx: Error executing a python function in exec_func_python() autogenerated: Exception: FileNotFoundError: [Errno 2] No such file or directory: '/home/pokybuild/yocto-worker/oe-selftest-armhost/build/build-st-2644812/tmp/deploy/spdx/qemuarm64/recipes/recipe-acl-native.spdx.json'
https://autobuilder.yoctoproject.org/typhoon/#/builders/65/builds/6964/steps/14/logs/stdio ERROR: nativesdk-linux-libc-headers-6.1-r0 do_create_spdx: The recipe nativesdk-linux-libc-headers is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/deploy/spdx/beaglebone-yocto/packages/nativesdk-linux-libc-headers-dbg.spdx.json (matched in manifest-i686_linux-nativesdk-linux-libc-headers.create_spdx) /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/deploy/spdx/beaglebone-yocto/packages/nativesdk-linux-libc-headers-dev.spdx.json (matched in manifest-i686_linux-nativesdk-linux-libc-headers.create_spdx) /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/deploy/spdx/beaglebone-yocto/recipes/recipe-nativesdk-linux-libc-headers.spdx.json (matched in manifest-i686_linux-nativesdk-linux-libc-headers.create_spdx) Please verify which recipe should provide the above files. The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_ALLOW_OVERLAP_FILES may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above. ERROR: nativesdk-linux-libc-headers-6.1-r0 do_create_spdx: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases. ERROR: nativesdk-libgcc-initial-12.2.0-r0 do_create_spdx: The recipe nativesdk-libgcc-initial is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/deploy/spdx/beaglebone-yocto/recipes/recipe-nativesdk-libgcc-initial.spdx.json (matched in manifest-i686_linux-nativesdk-libgcc-initial.create_spdx) Please verify which recipe should provide the above files. The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_ALLOW_OVERLAP_FILES may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above. ERROR: nativesdk-libgcc-initial-12.2.0-r0 do_create_spdx: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases. ERROR: nativesdk-gnu-config-20230216+gitAUTOINC+63acb96f92-r0 do_create_spdx: The recipe nativesdk-gnu-config is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/deploy/spdx/beaglebone-yocto/packages/nativesdk-gnu-config.spdx.json (matched in manifest-i686_linux-nativesdk-gnu-config.create_spdx) /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/deploy/spdx/beaglebone-yocto/recipes/recipe-nativesdk-gnu-config.spdx.json (matched in manifest-i686_linux-nativesdk-gnu-config.create_spdx) Please verify which recipe should provide the above files. The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_ALLOW_OVERLAP_FILES may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above. ERROR: nativesdk-gnu-config-20230216+gitAUTOINC+63acb96f92-r0 do_create_spdx: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases. ERROR: nativesdk-qemuwrapper-cross-1.0-r0 do_create_spdx: The recipe nativesdk-qemuwrapper-cross is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/deploy/spdx/beaglebone-yocto/packages/nativesdk-qemuwrapper-cross.spdx.json (matched in manifest-i686_linux-nativesdk-qemuwrapper-cross.create_spdx) /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/deploy/spdx/beaglebone-yocto/packages/nativesdk-qemuwrapper-cross-dev.spdx.json (matched in manifest-i686_linux-nativesdk-qemuwrapper-cross.create_spdx) /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/deploy/spdx/beaglebone-yocto/packages/nativesdk-qemuwrapper-cross-dbg.spdx.json (matched in manifest-i686_linux-nativesdk-qemuwrapper-cross.create_spdx) /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/deploy/spdx/beaglebone-yocto/recipes/recipe-nativesdk-qemuwrapper-cross.spdx.json (matched in manifest-i686_linux-nativesdk-qemuwrapper-cross.create_spdx) Please verify which recipe should provide the above files. The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_ALLOW_OVERLAP_FILES may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above. ERROR: nativesdk-qemuwrapper-cross-1.0-r0 do_create_spdx: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases. ERROR: meta-environment-beaglebone-yocto-1.0-r8 do_create_spdx: The recipe meta-environment-beaglebone-yocto is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/deploy/spdx/beaglebone-yocto/packages/meta-environment-beaglebone-yocto.spdx.json (matched in manifest-i686_i686-nativesdk-meta-environment-beaglebone-yocto.create_spdx) /home/pokybuild/yocto-worker/beaglebone/build/build/tmp/deploy/spdx/beaglebone-yocto/recipes/recipe-meta-environment-beaglebone-yocto.spdx.json (matched in manifest-i686_i686-nativesdk-meta-environment-beaglebone-yocto.create_spdx) Please verify which recipe should provide the above files. The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_ALLOW_OVERLAP_FILES may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above. ERROR: meta-environment-beaglebone-yocto-1.0-r8 do_create_spdx: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases.
https://autobuilder.yoctoproject.org/typhoon/#/builders/45/builds/6923/steps/12/logs/stdio ERROR: python3-bcrypt-4.0.1-r0 do_create_spdx: Error executing a python function in exec_func_python() autogenerated: Exception: FileNotFoundError: [Errno 2] No such file or directory: '/home/pokybuild/yocto-worker/musl-qemux86-64/build/build/tmp/deploy/spdx/qemux86-64/recipes/recipe-python3-pycparser-native.spdx.json' ERROR: gstreamer1.0-plugins-bad-1.22.0-r0 do_create_spdx: Error executing a python function in exec_func_python() autogenerated: Exception: FileNotFoundError: [Errno 2] No such file or directory: '/home/pokybuild/yocto-worker/no-x11/build/build/tmp/deploy/spdx/qemux86-64/recipes/recipe-spirv-headers-native.spdx.json' NOTE: Running task 9811 of 16177 (/home/pokybuild/yocto-worker/no-x11/build/meta/recipes-support/boost/boost-build-native_1.81.0.bb:do_create_spdx) ERROR: python3-cryptography-39.0.2-r0 do_create_spdx: Error executing a python function in exec_func_python() autogenerated: Exception: FileNotFoundError: [Errno 2] No such file or directory: '/home/pokybuild/yocto-worker/no-x11/build/build/tmp/deploy/spdx/qemux86-64/recipes/recipe-python3-pycparser-native.spdx.json'
https://autobuilder.yoctoproject.org/typhoon/#/builders/89/builds/6941/steps/16/logs/stdio ERROR: nativesdk-mingw-w64-headers-9.0.0-r0 do_create_spdx: The recipe nativesdk-mingw-w64-headers is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/recipes/recipe-nativesdk-mingw-w64-headers.spdx.json (matched in manifest-i686_mingw32-nativesdk-mingw-w64-headers.create_spdx) /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/packages/nativesdk-mingw-w64-headers-dbg.spdx.json (matched in manifest-i686_mingw32-nativesdk-mingw-w64-headers.create_spdx) /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/packages/nativesdk-mingw-w64-headers.spdx.json (matched in manifest-i686_mingw32-nativesdk-mingw-w64-headers.create_spdx) /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/packages/nativesdk-mingw-w64-headers-dev.spdx.json (matched in manifest-i686_mingw32-nativesdk-mingw-w64-headers.create_spdx) Please verify which recipe should provide the above files. The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_ALLOW_OVERLAP_FILES may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above. ERROR: nativesdk-mingw-w64-headers-9.0.0-r0 do_create_spdx: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases. ERROR: nativesdk-packagegroup-sdk-host-1.0-r12 do_create_spdx: The recipe nativesdk-packagegroup-sdk-host is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/recipes/recipe-nativesdk-packagegroup-sdk-host.spdx.json (matched in manifest-i686_mingw32-nativesdk-packagegroup-sdk-host.create_spdx) /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/packages/nativesdk-packagegroup-sdk-host.spdx.json (matched in manifest-i686_mingw32-nativesdk-packagegroup-sdk-host.create_spdx) Please verify which recipe should provide the above files. The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_ALLOW_OVERLAP_FILES may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above. ERROR: nativesdk-packagegroup-sdk-host-1.0-r12 do_create_spdx: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases. ERROR: packagegroup-cross-canadian-qemux86-1.0-r0 do_create_spdx: The recipe packagegroup-cross-canadian-qemux86 is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/recipes/recipe-packagegroup-cross-canadian-qemux86.spdx.json (matched in manifest-i686_i686-nativesdk-mingw32-packagegroup-cross-canadian-qemux86.create_spdx) /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/packages/packagegroup-cross-canadian-qemux86.spdx.json (matched in manifest-i686_i686-nativesdk-mingw32-packagegroup-cross-canadian-qemux86.create_spdx) Please verify which recipe should provide the above files. The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_ALLOW_OVERLAP_FILES may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above. ERROR: packagegroup-cross-canadian-qemux86-1.0-r0 do_create_spdx: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases. NOTE: Running task 2790 of 3560 (/home/pokybuild/yocto-worker/meta-mingw/build/meta/recipes-core/meta/meta-environment.bb:do_install) ERROR: nativesdk-qemuwrapper-cross-1.0-r0 do_create_spdx: The recipe nativesdk-qemuwrapper-cross is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/recipes/recipe-nativesdk-qemuwrapper-cross.spdx.json (matched in manifest-i686_mingw32-nativesdk-qemuwrapper-cross.create_spdx) /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/packages/nativesdk-qemuwrapper-cross-dbg.spdx.json (matched in manifest-i686_mingw32-nativesdk-qemuwrapper-cross.create_spdx) /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/packages/nativesdk-qemuwrapper-cross-dev.spdx.json (matched in manifest-i686_mingw32-nativesdk-qemuwrapper-cross.create_spdx) /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/packages/nativesdk-qemuwrapper-cross.spdx.json (matched in manifest-i686_mingw32-nativesdk-qemuwrapper-cross.create_spdx) Please verify which recipe should provide the above files. The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_ALLOW_OVERLAP_FILES may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above. ERROR: nativesdk-qemuwrapper-cross-1.0-r0 do_create_spdx: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases. ERROR: meta-environment-qemux86-1.0-r8 do_create_spdx: The recipe meta-environment-qemux86 is trying to install files into a shared area when those files already exist. Those files and their manifest location are: /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/recipes/recipe-meta-environment-qemux86.spdx.json (matched in manifest-i686_i686-nativesdk-mingw32-meta-environment-qemux86.create_spdx) /home/pokybuild/yocto-worker/meta-mingw/build/build/tmp/deploy/spdx/qemux86/packages/meta-environment-qemux86.spdx.json (matched in manifest-i686_i686-nativesdk-mingw32-meta-environment-qemux86.create_spdx) Please verify which recipe should provide the above files. The build has stopped, as continuing in this scenario WILL break things - if not now, possibly in the future (we've seen builds fail several months later). If the system knew how to recover from this automatically it would, however there are several different scenarios which can result in this and we don't know which one this is. It may be you have switched providers of something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you need to execute the clean task for both recipes and it will resolve this error. It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. Cleaning those recipes should again resolve this error, however switching DISTRO_FEATURES on an existing build directory is not supported - you should really clean out tmp and rebuild (reusing sstate should be safe). It could be the overlapping files detected are harmless in which case adding them to SSTATE_ALLOW_OVERLAP_FILES may be the correct solution. It could also be your build is including two different conflicting versions of things (e.g. bluez 4 and bluez 5 and the correct solution for that would be to resolve the conflict. If in doubt, please ask on the mailing list, sharing the error and filelist above. ERROR: meta-environment-qemux86-1.0-r8 do_create_spdx: If the above message is too much, the simpler version is you're advised to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix things in most (but not all) cases.
Hello everyone, Just wanted to share that we're also reproducing this issue. We've tried adding INHERIT += "create-spdx" to our builds, and because we're using the same cache of our previous builds (without inheriting create-spdx), we get this failure: ERROR: kernel-module-imx-gpu-viv-6.4.3.p4.6+fslc+gitAUTOINC+1adf982c59-r0 do_create_runtime_spdx: Error executing a python function in exec_func_python() autogenerated: The stack trace of python calls that resulted in this exception/failure was: File: 'exec_func_python() autogenerated', lineno: 2, function: <module> 0001: *** 0002:do_create_runtime_spdx(d) 0003: File: '/torizon-integration-kirkstone/torizon/build-torizon/conf/../../layers/openembedded-core/meta/classes/create-spdx.bbclass', lineno: 726, function: do_create_runtime_spdx 0722: (dep_spdx_package, dep_package_ref) = dep_package_cache[dep] 0723: else: 0724: dep_path = deploy_dir_spdx / "packages" / ("%s.spdx.json" % dep_pkg) 0725: *** 0726: spdx_dep_doc, spdx_dep_sha1 = oe.sbom.read_doc(dep_path) 0727: 0728: for pkg in spdx_dep_doc.packages: 0729: if pkg.name == dep_pkg: 0730: dep_spdx_package = pkg File: '/torizon-integration-kirkstone/torizon/build-torizon/conf/../../layers/openembedded-core/meta/lib/oe/sbom.py', lineno: 67, function: read_doc 0063: else: 0064: with fn.open("rb") as f: 0065: yield f 0066: *** 0067: with get_file() as f: 0068: sha1 = hashlib.sha1() 0069: while True: 0070: chunk = f.read(4096) 0071: if not chunk: File: '/usr/lib/python3.9/contextlib.py', lineno: 117, function: __enter__ 0113: # do not keep args and kwds alive unnecessarily 0114: # they are only needed for recreation, which is not possible anymore 0115: del self.args, self.kwds, self.func 0116: try: *** 0117: return next(self.gen) 0118: except StopIteration: 0119: raise RuntimeError("generator didn't yield") from None 0120: 0121: def __exit__(self, type, value, traceback): File: '/torizon-integration-kirkstone/torizon/build-torizon/conf/../../layers/openembedded-core/meta/lib/oe/sbom.py', lineno: 64, function: get_file 0060: def get_file(): 0061: if isinstance(fn, io.IOBase): 0062: yield fn 0063: else: *** 0064: with fn.open("rb") as f: 0065: yield f 0066: 0067: with get_file() as f: 0068: sha1 = hashlib.sha1() File: '/usr/lib/python3.9/pathlib.py', lineno: 1241, function: open 1237: """ 1238: Open the file pointed by this path and return a file object, as 1239: the built-in open() function does. 1240: """ *** 1241: return io.open(self, mode, buffering, encoding, errors, newline, 1242: opener=self._opener) 1243: 1244: def read_bytes(self): 1245: """ File: '/usr/lib/python3.9/pathlib.py', lineno: 1109, function: _opener 1105: pass 1106: 1107: def _opener(self, name, flags, mode=0o666): 1108: # A stub for the opener argument to built-in open() *** 1109: return self._accessor.open(self, flags, mode) 1110: 1111: def _raw_open(self, flags, mode=0o777): 1112: """ 1113: Open the file pointed by this path and return a file descriptor, Exception: FileNotFoundError: [Errno 2] No such file or directory: '/torizon-integration-kirkstone/torizon/build-torizon/deploy/spdx/verdin-imx8mm/packages/kernel-5.15.77-6.2.0-devel+git.2276f375f152.spdx.json' ERROR: Logfile of failure stored in: /torizon-integration-kirkstone/torizon/build-torizon/tmp/work/verdin_imx8mm-tdx-linux/kernel-module-imx-gpu-viv/6.4.3.p4.6+fslc+gitAUTOINC+1adf982c59-r0/temp/log.do_create_runtime_spdx.15853 ERROR: Task (/torizon-integration-kirkstone/torizon/build-torizon/conf/../../layers/meta-freescale/recipes-kernel/kernel-modules/kernel-module-imx-gpu-viv_6.4.3.p4.6+fslc.bb:do_create_runtime_spdx) failed with exit code '1' If we build from scratch or clean the cache, then the error is also gone.
SPDX enabled by default in poky here: https://git.yoctoproject.org/poky/commit/?id=581edf20120cd383e8dea0693239629e7547bb7e There were many fixed merged shortly before that which resolved several different failure modes, e.g. https://git.yoctoproject.org/poky/commit/?id=42071227f6f54055d8ac44126ab1d95f83f5b264 The v86d change: https://git.yoctoproject.org/poky/commit/?id=0498637354387cea2b305cebb2c102ef5de2848b was particularly unclear.