-
Notifications
You must be signed in to change notification settings - Fork 149
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
Partial SPDX detection lead to failing lint in 2.0 #771
Comments
This is not the only file that is failing:
file content:
dep5:
|
Using a
|
Hey @mrdrogdrog, We anticipated that the (now defined and enforced) order of precedence will cause some problems but internally came to the conclusion that it's still needed (hence the new major version).
The warning should persist in this case but REUSE compliance should again be achieved. Is that not the case? What is the exit of this command when you use the
The warning is there just to make sure that the user is aware that there are multiple sources of information but only one is used. |
Creating .license files worked. So it seems like the hierarchy is
It would be nice if you would add a mention to the README about this. :) |
May I ask what you mean by "snippet detection"? A snippet should be treated the same way as a comment on the file header AFAIK. |
Oh sure. I'm not sure if it's the right term. I mean the partial detection of license information. |
This change is documented in two places, but may need to be documented in more. Currently:
Future:
|
I honor the effort which went into the new features, but I also thinkt that the new behaviour is not intuitive. I suggest that files which are explicitly excluded in dep5 are treated as excluded and should not raise errors.
|
Thanks for taking care so quickly ❤️ |
Hello,
we tried to update reuse to 2.0 but it fails when linting our files and we assume that the snippet detection is the culprit.
Following situation:
Our repository contains a file for JetBrains IDEs so it can automatically renew/add a copyright to source files.
To make the linter happy we have a rule in our dep5 file that applies to this file:
Now here comes the problem:
Reuse 2 scans this file, finds the SPDX snippet and assues another license.
Which results in a failure:
Is there any way to deactivate the snippet detection? Or to exclude files?
The text was updated successfully, but these errors were encountered: