Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Pinned dependency causes conflict

See original GitHub issue

Latest paket, I have a dependencies file which I have reduced to: -

source https://nuget.org/api/v2
nuget Microsoft.ApplicationInsights.WindowsServer = 1.2.3

This does not work, although (as far as I can see) it should.

Resolving packages for group Main:
 - Microsoft.ApplicationInsights.WindowsServer is pinned to 1.2.3
 - Microsoft.ApplicationInsights 1.2.3
 - Microsoft.ApplicationInsights.DependencyCollector 2.0.0
 - Microsoft.ApplicationInsights.PerfCounterCollector 2.0.0
 - Microsoft.ApplicationInsights.WindowsServer.TelemetryChannel 2.0.0
 - Microsoft.Diagnostics.Tracing.EventSource.Redist 1.1.28
 - Microsoft.ApplicationInsights.PerfCounterCollector 1.2.3
 - Microsoft.ApplicationInsights.DependencyCollector 1.2.3
Paket failed with:
        There was a version conflict during package resolution.
  Resolved packages:
   - Microsoft.ApplicationInsights 1.2.3
   - Microsoft.ApplicationInsights.DependencyCollector 1.2.3
   - Microsoft.ApplicationInsights.PerfCounterCollector 1.2.3
   - Microsoft.ApplicationInsights.WindowsServer 1.2.3
   - Microsoft.ApplicationInsights.WindowsServer.TelemetryChannel 2.0.0
  Could not resolve package Microsoft.ApplicationInsights:
   - Microsoft.ApplicationInsights.DependencyCollector 2.0.0 requested: 2.0.0
   - Microsoft.ApplicationInsights.PerfCounterCollector 1.2.3 requested: 1.2.3
   - Microsoft.ApplicationInsights.WindowsServer 1.2.3 requested: 1.2.3

  Please try to relax some conditions.

It seems to be pulling in version 2.0 dependencies for some reason…

Issue Analytics

State:
Created 8 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

forkicommented, Mar 16, 2016

please give it another try

1reaction

forkicommented, Mar 16, 2016

I think https://github.com/fsprojects/Paket/pull/1521/commits/28d9b82b226cb03d56fa7b2c42466dadedb27727#diff-781e85b03afcc7c6cedfbd46e3d3b607R430 solves it.

Top Results From Across the Web

Fix the upstream dependency conflict installing NPM ...

It looks like it's a problem with peer dependencies in the latest version of npm (v7) which is still a beta version. Try...

If you publish a Python library with pinned dependencies ...

If you publish a Python library with pinned dependencies, your code is broken as soon as someone tries to use it with another...

The Nine Circles of Python Dependency Hell | by Knewton

“Dependency hell” is a term for the frustration that arises from problems with transitive (indirect) dependencies. Dependency hell in Python often happens ...

How to Automatically Eliminate Dependency Hell

Wrestling with Dependency Hell? Understand how the ActiveState Platform can help you automatically resolve dependency conflicts.

How to identify and resolve a dependency conflict

This can often be caused by unpinned dependencies, when a package is listed as a requirement without specifying a version. In this example,...