On Wed, Jun 10, 2026 at 7:17 AM Mathieu Dubois-Briand <[email protected]> wrote: > > On Wed Jun 10, 2026 at 12:15 AM CEST, Joshua Watt via lists.openembedded.org > wrote: > > The SPDX use case for file system image has been well defined since SPDX > > was first implemented, however there has always been a desire to also > > express SPDX output for other non-image deliverables (primarily, those > > that have a do_deploy task or similar). These types of tasks cannot > > easily use the traditional method of having a separate SPDX task that > > runs to create their SPDX output as this causes lots of problems with > > the way dependencies are specified. Instead, it is desirable for these > > tasks to directly produce SPDX output that can be consumed by other > > tasks that depend on them. > > > > This patch series adds support for this. Any sstate task can now be > > added to the SPDX_DEPLOY_TASKS list and it will run a postfunc to > > generate SPDX output that describes what is being deployed. For > > classical do_deploy tasks, this is setup to be easy by automatically > > capturing all the deployed output files in the SPDX data, but other > > tasks can be added as well. > > > > Finally, the do_create_image_spdx task is removed and replaced with a > > SPDX deploy postfunc using this new system. This means that any task > > that depends on do_image_complete will automatically also get the SPDX > > output for the image, simplifying the dependency handling. > > > > Joshua Watt (5): > > Hi Joshua, > > Thanks for your series. I believe we are seeing both a new error and new > warnings because of it. > > > ERROR: grub-efi-2.14-r0 do_deploy_setscene: Recipe grub-efi is trying to > install files into a shared area when those files already exist. The files > and the manifests listing them are: > > /srv/pokybuild/yocto-worker/wic/build/build/tmp/deploy/spdx/3.0.1/core2-32/deploy/grub-efi-do_deploy-deploy.spdx.json > (matched in manifest-qemux86-grub-efi.deploy) > > /srv/pokybuild/yocto-worker/wic/build/build/tmp/deploy/spdx/3.0.1/core2-32/by-task/grub-efi:do_deploy.spdx.json > (matched in manifest-qemux86-grub-efi.deploy) > > /srv/pokybuild/yocto-worker/wic/build/build/tmp/deploy/spdx/3.0.1/core2-32/by-spdxid-hash/3c/3c29614c1a202bc0cc0a6f3dfd5b29235ea75ce5ee5bb0a847367bd8ce978004.spdx.json > (matched in manifest-qemux86-grub-efi.deploy) > Please adjust the recipes so only one recipe provides a given file. > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/15/builds/3852
This is caused because the grub-efi recipe changes subtly between qemux86 and genericx86: From bitbake -S printdiff: Variable GRUB_IMAGE value changed from 'grub-efi-bootia32.efi' to 'bootia32.efi' Variable GRUB_IMAGE_PREFIX value changed from '' to 'grub-efi- However, the recipe arch is PACKAGE_ARCH, which is the same for both machines. I _think_ this means that grub-ef should be change to be MACHINE_ARCH instead, since its expected(?) that it will change based on machine and not just PACKAGE_ARCH, but I'm not sure about that. Alternatively (or maybe in addition to), perhaps do_deploy SPDX output should always be written to a per-machine SPDX directory instead of using SSTATE_ARCH? This has congruence with DEPLOY_DIR_IMAGE containing MACHINE. I think this wouldn't actually work though because DEPLOY_DIR_IMAGE is an sstate output directory (so I think it can change without invalidating the task), where as SPDX is writing to SSTATE_ARCH as an sstate input directory. > > > WARNING: core-image-minimal-1.0-r0 do_create_deploy_sbom: The following SPDX > IDs were unable to be resolved: > > http://spdxdocs.org/openembedded-alias/by-doc-hash/500473e510f927d1a990e932c4942f978ce9da778692ab840dec17ad0ece09a1/pigz-native/UNIHASH/build/recipe > > https://autobuilder.yoctoproject.org/valkyrie/#/builders/15/builds/3852 > https://autobuilder.yoctoproject.org/valkyrie/#/builders/10/builds/3887 > https://autobuilder.yoctoproject.org/valkyrie/#/builders/65/builds/3874 > > Can you have a look at the issues? > > Thanks, > Mathieu > > -- > Mathieu Dubois-Briand, Bootlin > Embedded Linux and Kernel engineering > https://bootlin.com >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#238585): https://lists.openembedded.org/g/openembedded-core/message/238585 Mute This Topic: https://lists.openembedded.org/mt/119731700/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
