Skip to content
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

Closed
Jeeppler opened this issue Sep 16, 2022 · 5 comments · Fixed by #1196
Closed

Debian-inspector conflict while using scancode and tern #1185

Jeeppler opened this issue Sep 16, 2022 · 5 comments · Fixed by #1196

Comments

@Jeeppler
Copy link

Jeeppler commented Sep 16, 2022

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

tern==2.10.1
scancode-toolkit[full]==31.1.1

Error in terminal

ERROR: Cannot install -r packages.txt (line 1), -r /packages.txt (line 2) and scancode-toolkit[full]==31.1.1 because these package versions have conflicting dependencies.

The conflict is caused by:
    scancode-toolkit[full] 31.1.1 depends on debian-inspector>=31.0.0
    scancode-toolkit 31.1.1 depends on debian-inspector>=31.0.0
    tern 2.10.1 depends on debian-inspector==30.0.0

Expected behavior

Scancode-toolkit and Tern use the same debian-inspector version.

Environment you are running Tern on

  • Python version: 3.9
@vargenau
Copy link
Contributor

vargenau commented Dec 8, 2022

See also #1195

@rnjudge
Copy link
Contributor

rnjudge commented Dec 8, 2022

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.

@Jeeppler
Copy link
Author

Jeeppler commented Dec 8, 2022

@rnjudge thanks for your reply. I am looking forward to the release.

rnjudge added a commit to rnjudge/tern that referenced this issue Dec 9, 2022
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 <rjudge@vmware.com>
@rnjudge
Copy link
Contributor

rnjudge commented Dec 9, 2022

I'm not sure why pip thinks Tern depends on debian-inspector==30.0.0 when requirements.txt says debian-inspector>=30.0 but nevertheless it will be fixed in the upcoming release.

rnjudge added a commit that referenced this issue Dec 9, 2022
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 <rjudge@vmware.com>
@Jeeppler
Copy link
Author

@rnjudge thanks for fixing it.

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 a pull request may close this issue.

3 participants