-
Notifications
You must be signed in to change notification settings - Fork 188
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
Debian-inspector conflict while using scancode and tern #1185
Comments
See also #1195 |
Thanks for the issue @Jeeppler! I apologize for the delay.. I have been on maternity leave. I will get the debian-inspector dependency updated for Tern. There will be a new release before the holidays. |
@rnjudge thanks for your reply. I am looking forward to the release. |
Installing Scancode-toolkit 31.1.1 and Tern 2.10.1 together results in a package conflict because both rely on a different version of the debian-inspector package. This commit resolves that conflict. Resolves tern-tools#1185 Signed-off-by: Rose Judge <[email protected]>
I'm not sure why pip thinks Tern depends on |
Installing Scancode-toolkit 31.1.1 and Tern 2.10.1 together results in a package conflict because both rely on a different version of the debian-inspector package. This commit resolves that conflict. Resolves #1185 Signed-off-by: Rose Judge <[email protected]>
@rnjudge thanks for fixing it. |
Describe the bug
Installing Scancode-toolkit 31.1.1 and Tern 2.10.1 together results in a package conflict, because both rely on a different version of the
debian-inspector
package.To Reproduce
Try to install Scancode-toolkit 31.1.1 and Tern 2.10.1 together.
packages.txt
Error in terminal
Expected behavior
Scancode-toolkit and Tern use the same
debian-inspector
version.Environment you are running Tern on
The text was updated successfully, but these errors were encountered: