-
Notifications
You must be signed in to change notification settings - Fork 27
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
deltacode doesn't support the new json format of scancode over 3.0 #122
Comments
@macrovve excellent catch! You surely can fix it and that will be mucho welcomed! |
@pombredanne @MaJuRG is there any way to use deltacode for comparing the scans of two json from scancode over 3.0?? |
@Pratikrocks it should. What errors are you getting? |
this is the error i was receiving and i used delta code via the command the headers for -n file is and the header for the -o file path is |
@MaJuRG Upon scanning with scancode 3.X the |
ill take a look, thanks for this |
@MaJuRG then i need to use scancode version 2.x for testing the functionalities of deltacode? |
@Pratikrocks I have just tested DeltaCode and it works fine on Scancode v3 scans. I am not sure what issue you are experiencing. Perhaps you have an old version of deltacode? I would run off the |
@MaJuRG sir I downloaded the .zip file from |
@Pratikrocks Good point. That release is a bit out of date. I will cut an updated release shortly. For now, you should clone this repo via |
@MaJuRG okay sir |
Addresses: aboutcode-org#113, aboutcode-org#122 Signed-off-by: Steven Esser <sesser@nexb.com>
Addresses: aboutcode-org#113, aboutcode-org#122 Signed-off-by: Steven Esser <sesser@nexb.com>
When I used the json file generate by scancode 3.0.2, It raise an exception.
And here are the head of two sample file:
And here are the source code. The reason why raise exception is the scancode_version has been change to tool_version in scancode 3.0+.
but I cannot find #171 information in TODO. it seems easy to fix. Can I work on it?
The text was updated successfully, but these errors were encountered: