-
Notifications
You must be signed in to change notification settings - Fork 155
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
linter does not support dep5 of git submodules #163
Comments
This version is outdated. Can you try with a newer version? Newer versions of reuse should—by default—completely ignore submodules unless you do |
Hi @carmenbianca (I notice now I heard you speaking at the SFScon! 😊), yes you'r right: I updated the tool, now I'm running version |
I am running latest git version of reuse as of today (exactly |
What would we want to happen, optimally?
|
I am not sure it would be good to use (my feeling is rather, not so much, as it would be too manual/work intensive), but as it seems not to exist, I would say it makes little sense that we go deeper into it. |
Not sure on the status of this, but going back to the original posters problem. |
Steps to reproduce
Create a new reuse project under git. Add a git submodule which is compliant with the reuse specification, but covers some files with debian's dep5 mechanism. If you run the linter on the parent directory (not the submodule), it will complain that the submodule is not reuse complaint.
Example
Let's create an empty git repo first, add the submodule and check its complaincy:
Now make a step back and check from the parent git repo.
Hint
I'm not a python fan and I did not dig into the code, but it looks like
reuse
is not taking into consideration nested.reuse
folders.Context
OS:
Darwin jecoz.local 19.2.0 Darwin Kernel Version 19.2.0: Sat Nov 9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64 x86_64
reuse version:
reuse 0.5.2
The text was updated successfully, but these errors were encountered: