Skip to content

Conversation

rzr
Copy link

@rzr rzr commented Sep 26, 2025

I noticed while using https://reuse.software/
this false positive error:

reuse.extract - ERROR - Could not parse 'MIT\n','
reuse.extract - ERROR - \
  '.../FreeRTOS-Kernel/.github/scripts/kernel_checker.py' \
  holds an SPDX expression that cannot be parsed, skipping the file

Relate-to: #1321

Description

Test Steps

Checklist:

  • I have tested my changes. No regression in existing tests.
  • I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I noticed while using https://reuse.software/
this false positive error:

    reuse.extract - ERROR - Could not parse 'MIT\n','
    reuse.extract - ERROR - \
      '.../FreeRTOS-Kernel/.github/scripts/kernel_checker.py' \
      holds an SPDX expression that cannot be parsed, skipping the file

Origin: FreeRTOS#1322
Relate-to: FreeRTOS#1321
Signed-off-by: Philippe Coval <philippe.coval@silabs.com>
Copy link

@aggarg
Copy link
Member

aggarg commented Sep 29, 2025

This line does not need to be parsed by the tool as it is not license. Seems more like a tool limitation.

@rzr
Copy link
Author

rzr commented Sep 29, 2025

This line does not need to be parsed by the tool as it is not license. Seems more like a tool limitation.

yes i can confirm , that's why i committed as a workaround
Feel free to ignore if you think it is polluting the code, but it helped me to scan some repository that pull freertos as submodule dependency.

moninom1 pushed a commit to moninom1/FreeRTOS-Kernel that referenced this pull request Sep 30, 2025
Signed-off-by: Gaurav Aggarwal <aggarg@amazon.com>
@xuelix
Copy link
Member

xuelix commented Oct 3, 2025

The reuse tool needs to be updated in this case.
Close the PR.

@xuelix xuelix closed this Oct 3, 2025
@rzr
Copy link
Author

rzr commented Oct 4, 2025

The reuse tool needs to be updated in this case. Close the PR.

ok fair enough, I will try to forward the issue at the source

meanwhile please consider:

#1321

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants