Marc-Etienne Vargenau
Marc-Etienne Vargenau
> @rnjudge: `tern report -i photon:3.0 -f spdxjson -sv 2.3 -o output.json` followed by `pyspdxtools -i output.json` yields no errors or invalidations, so I'll mark this "Ready for review" now....
> I meant `-sv`, this was changed according to [this comment](https://github.com/tern-tools/tern/pull/1233#discussion_r1266006186). Thank you, I had missed that comment.
Hi @rnjudge, Thank you for taking our request under consideration. Currently, the messages are put in the PackageComment of each affected package. It would be better to have them grouped...
See https://github.com/fossology/fossology/pull/2628
@GMishx Hi, I have implemented the changes you requested, but now I have some tests failing, and I do not understand what the errors are.
@sej7278 Unfortunately, this bug does not seem to get much interest. It is a pity, as the SPDX code is invalid.
> @vargenau i guess we could use sed to replace / with ./ on the sbom output, its far from ideal though Yes, it is what I am doing, but...
I tested again with version 0.25.0 of cyclonedx-cli The `hello.spdx.json` file is valid SPDX: ``` pyspdxtools -i hello2.spdx.json ``` When converted to CycloneDX then converted back to SPDX, the resulting...
[hello2.spdx.json.txt](https://github.com/CycloneDX/cyclonedx-cli/files/15404187/hello2.spdx.json.txt)
@bact @zvr @goneall Can someone please merge this trivial change?