You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the SPDX document appears to contain no packages and 27 relationships for the Helics. Unfortunately I'm not terribly familiar with SPDX, and don't know if a package is required.
Interesting - I suspect the SPDX Python library released another update recently that changes their validation function.
SPDX wanting a package is a bit of a pain since often we don’t really know what “package” files belong to.. I wonder if we can make it happy by adding a SPDXRef-DOCUMENT DESCRIBES or DESCRIBED_BY using NOASSERTION instead of creating a fake package with no real information.
I just encountered this when testing Surfactant on my own project.
[]
Document is not valid. The following errors were detected: [ValidationMessage(validation_message='there must be at least one relationship "SPDXRef-DOCUMENT DESCRIBES ..." or "... DESCRIBED_BY SPDXRef-DOCUMENT" when there is not only a single package present', context=ValidationContext(spdx_id='SPDXRef-DOCUMENT', parent_id=None, element_type=<SpdxElementType.DOCUMENT: 7>, full_element=None))]
I'll see if the NOASSERTION method described above works; otherwise, is there any default information you'd expect a "fake" SPDX package to contain that's just meant to make the SPDX library validator happy?
Describe the bug
With the Helics image surfactant currently fails to generate an output in the SPDX format.
To Reproduce
Steps to reproduce the behavior:
pip install -e .
surfactant create-config Helics-3.5.0-Linux-x86_64
surfactant generate Helics-3.5.json --output_format spdx helics_spdx.json
Expected behavior
We should expect surfactant to be able to generate a SPDX BOM with the helics firmware.
System Information (please complete the following information):
Additional context
This may outline the need for tests for different output formats.
The text was updated successfully, but these errors were encountered: