-
Notifications
You must be signed in to change notification settings - Fork 6.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exporting SBOM fails: 'NoneType' object pkg.targetBuildFile has no attribute 'abspath' #71631
Comments
As you can see from the logs, Can you please run See commit c2ae5b3 why. |
Hi @traluke! We appreciate you submitting your first issue for our open-source project. 🌟 Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙 |
Hi @marc-hb,
|
@traluke it looks like you're running a version of Zephyr from before this fix mentioned by @marc-hb was introduced, based on the line numbers in your error log. |
Thanks! Can you please:
By transfering this bug from the "west" repo I made you skip all these "mandatory" questions but please take a look at them now: You can also try this: --- a/scripts/west_commands/zspdx/walker.py
+++ b/scripts/west_commands/zspdx/walker.py
@@ -516,6 +516,7 @@ class Walker:
# create relationship data between build files
rd = RelationshipData()
rd.ownerType = RelationshipDataElementType.FILENAME
+ log.warn(f'TRALUKE: {pkg},{pkg.targetBuildFile}')
rd.ownerFileAbspath = pkg.targetBuildFile.abspath
rd.otherType = RelationshipDataElementType.FILENAME
rd.otherFileAbspath = depAbspath |
@kartben, @marc-hb Please find the requested template filled below: name: SPDX Command Fails If the bug is for a project fork (such as NCS) specific feature, please open an issue in the fork project Sorry, to late for that. Should I create a new issue in the NCS project, Describe the bug Please also mention any information which could help others to understand
To Reproduce
Expected behavior Impact Logs and console output
Environment (please complete the following information):
|
Can you try to reproduce "upstream" = without NCS/NRF? |
Unfortunately we have our dev environment tightly integrated with NCF/NRF. However, I was quickly able to test it with |
That's weird. Could you post the error log for that one too? |
Thank you for your help! I copied the same snippet as before for the
|
OK so it looks like this was fixed in #66182 (and not the commit mentioned earlier), which unfortunately is part of the 3.6.0 release, and introduced after NCS' v.3.5.9-ncs1. Not sure there is a good solution for you until NCS updates their Zephyr version, which it looks like they might do in a future 2.6.x release looking at their current repo. |
this is not an issue in upstream zephyr, closing. |
I tried to export the SBOM according to the documentation, however, the last command fails with below error:
Found also that somebody else was struggling with it online: https://devzone.nordicsemi.com/f/nordic-q-a/91659/how-to-generate-sbom
Any suggestions?
cc: @swinslow
The text was updated successfully, but these errors were encountered: