From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: "Marta Rybczynska" <rybczynska@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org,
Marta Rybczynska <marta.rybczynska@syslinbit.com>
Subject: Re: [OE-core] [RFC][OE-core 0/7] SPDX3 Proof-of-Concept
Date: Fri, 27 Oct 2023 09:37:28 +0200 [thread overview]
Message-ID: <20231027093728.6b488b6e@booty> (raw)
In-Reply-To: <20231026105033.257971-1-marta.rybczynska@syslinbit.com>
Hello Marta,
On Thu, 26 Oct 2023 12:48:40 +0200
"Marta Rybczynska" <rybczynska@gmail.com> wrote:
> This patch-set adds a proof-of-concept implementation of the upcoming
> SPDX3 standard to the SBOM generation of the Yocto Project/OpenEmbedded.
>
> The current code delivers an equivalent of what is produced for SPDX2.2.
> The standard has not been released yet, and there is some specification
> work in progress still. Our questions and open points are available
> in the README.SPDX3 file.
>
> Also, this first RFC delivery will be followed by another one with
> SPDX assembly and the Licensing profile.
I ran this series on the autobuilders and it's triggering:
2023-10-26 22:30:42,532 - oe-selftest - INFO - 2: 27/33 214/548 (53.63s) (0 failed) (spdx.SPDXCheck.test_spdx_base_files)
2023-10-26 22:30:42,532 - oe-selftest - INFO - testtools.testresult.real._StringException: Traceback (most recent call last):
File "/home/pokybuild/yocto-worker/oe-selftest-fedora/build/meta/lib/oeqa/selftest/cases/spdx.py", line 54, in test_spdx_base_files
self.check_recipe_spdx("packages", "base-files.spdx.json", "base-files")
File "/home/pokybuild/yocto-worker/oe-selftest-fedora/build/meta/lib/oeqa/selftest/cases/spdx.py", line 51, in check_recipe_spdx
result = check_spdx_json(full_file_path)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/pokybuild/yocto-worker/oe-selftest-fedora/build/meta/lib/oeqa/selftest/cases/spdx.py", line 44, in check_spdx_json
self.assertNotEqual(report["SPDXID"], None)
~~~~~~^^^^^^^^^^
KeyError: 'SPDXID'
https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/5969/steps/14/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/5969/steps/14/logs/stdio
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-10-27 7:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 10:48 [RFC][OE-core 0/7] SPDX3 Proof-of-Concept Marta Rybczynska
2023-10-26 10:48 ` [RFC][OE-core 1/7] create-spdx-3.0: copy 2.2 class Marta Rybczynska
2023-10-26 10:48 ` [RFC][OE-core 2/7] oe/spdx: extend spdx.py objects Marta Rybczynska
2023-10-26 10:48 ` [RFC][OE-core 3/7] oe/sbom: change the write_doc to prepare for spdx3 Marta Rybczynska
2023-10-26 10:48 ` [RFC][OE-core 4/7] create-spdx-3.0: SPDX3 objects as classes Marta Rybczynska
2023-10-26 10:48 ` [RFC][OE-core 5/7] oe/sbom: search into json Marta Rybczynska
2023-10-26 10:48 ` [RFC][OE-core 6/7] README.SPDX3: add file Marta Rybczynska
2023-10-26 10:48 ` [RFC][OE-core 7/7] create-spdx-3.0: support for recipe spdx creation Marta Rybczynska
2023-10-27 7:37 ` Luca Ceresoli [this message]
[not found] ` <1791E6C172CE81BE.2594@lists.openembedded.org>
2023-10-27 7:40 ` [OE-core] [RFC][OE-core 0/7] SPDX3 Proof-of-Concept Luca Ceresoli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231027093728.6b488b6e@booty \
--to=luca.ceresoli@bootlin.com \
--cc=marta.rybczynska@syslinbit.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=rybczynska@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox