You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to nuget.org, Microsoft.ApplicationInsights.WindowsServer v1.2.3 requires = 1.2.3 of Microsoft.ApplicationInsights and >= 1.2.3 for it's other dependencies. That's why Paket tries to get v2.0.0 of Microsoft.ApplicationInsights.*.
You could use strategy: min, to emulate NuGet's behavior of downloading the oldest compatible version. This should get v1.2.3 of every package, which Microsoft.ApplicationInsights.WindowsServer depends on.
match !state with
| Resolution.Conflict(_,_,stillOpen,_,_)
when stillOpen |> Set.exists (fun r -> r = currentRequirement || r.Graph |> List.contains currentRequirement) |> not ->
forceBreak := true
| _ -> ()
If I comment this block out then it finds a resolution.
Yeah works now! Interestingly I still get up to 2.x for some of the transitive dependencies - is there a way to stop this aside from adding those manually into the .dependencies file?
Yes now you can try to change the strategy to min.
On Mar 16, 2016 11:20 AM, "Isaac Abraham" notifications@github.com wrote:
Yeah works now! Interestingly I still get up to 2.x for some of the
transitive dependencies - is there a way to stop this aside from adding
those manually into the .dependencies file?
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub #1520 (comment)
Activity
inosik commentedon Mar 16, 2016
According to nuget.org,
Microsoft.ApplicationInsights.WindowsServer v1.2.3requires = 1.2.3 ofMicrosoft.ApplicationInsightsand >= 1.2.3 for it's other dependencies. That's why Paket tries to get v2.0.0 ofMicrosoft.ApplicationInsights.*.You could use
strategy: min, to emulate NuGet's behavior of downloading the oldest compatible version. This should get v1.2.3 of every package, whichMicrosoft.ApplicationInsights.WindowsServerdepends on.forki commentedon Mar 16, 2016
I believe strategy:min vs max should not result in conflict vs. non-conflict since it only changes order. I'll take a deeper look
forki commentedon Mar 16, 2016
I'm pretty sure this is a bug, but not sure where exactly yet
forki commentedon Mar 16, 2016
@mrinaldi
It has something to do with this optimization:
If I comment this block out then it finds a resolution.
Force resolver to look into deeper levels - fixes #1520
Force resolver to look into deeper levels - fixes #1520
forki commentedon Mar 16, 2016
I think 28d9b82#diff-781e85b03afcc7c6cedfbd46e3d3b607R430 solves it.
forki commentedon Mar 16, 2016
please give it another try
isaacabraham commentedon Mar 16, 2016
Yeah works now! Interestingly I still get up to 2.x for some of the transitive dependencies - is there a way to stop this aside from adding those manually into the .dependencies file?
forki commentedon Mar 16, 2016
Yes now you can try to change the strategy to min.
On Mar 16, 2016 11:20 AM, "Isaac Abraham" notifications@github.com wrote:
isaacabraham commentedon Mar 16, 2016
Hmmm. Yes that works as well although not quite what I'm thinking, which is more "don't go above 'major' version of transitive dependencies".
I guess this is more about the package author of A (not specifying deps version boundaries tightly enough) than paket though, right?
forki commentedon Mar 16, 2016
yes that is something that can't be really expressed in nuget
Revert #1520
Revert #1520