-
Notifications
You must be signed in to change notification settings - Fork 525
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
Paket do not keeps versions locked for dependencies #1457
Comments
The indented lines are only showing the restrictions from the package nuspec. They are combined with the stuff that you specify in the dependencies file. As a result you see that we select the correct versions. |
In other words: indented lines are only for information. They don't represent what we select |
Ok I see that when I create nuget packages the dependencies from paket.dependencies are not used in nuspec |
Or maybe I don't understand what you are describing. |
I will try again :) I created some nuget let's call it Common.dll, that has dependency on 3 Microsoft.Orleans nugets of specific version, I checked the nuspec file and it looks like all dependencies there are correct, here a sample:
But when I use the Common.dll nuget in my other project I don't get 1.1.1 versions but get 1.1.2 version of Orleans dependencies. |
Ok I see the issue is the forma of the version it writen as version="1.1.1" but it should be specified as version="[1.1.1]" 1.0 = 1.0 ≤ x |
dependency id="Microsoft.Orleans.OrleansRuntime" version="1.1.1" means >= 1.1.1 |
Now i don't understand |
sorr reformatted |
Yes but in paket i wrote it as specific version |
are you sure? Can I see a repro? |
wait a minute. I think I can reproduce |
You can use the samples I used in first post. |
mhm. sorry I can't reproduce. 050bafb shows correct behaviour. |
Hi I am attached scenario that can reproduce it, just rename file to zip |
If I do pack I get:
|
I use following command to pack: paket pack output nugets minimum-from-lock-file buildplatform x64 |
Why didn't you say that before? ;-) |
From my point of view every one should use minimum-from-lock-file exclusively :) |
nope, that's only one of possible workflows. |
anyways will add a test and a fix for that |
Thank you |
please try latest |
Works perfect thank you |
Hi have following paket.dependencies file I set all 3 dependencies to be locked to specific version
source https://www.nuget.org/api/v2/
framework: net451
redirects: on
nuget Microsoft.Orleans.Core 1.1.1
nuget Microsoft.Orleans.CounterControl 1.1.1
nuget Microsoft.Orleans.OrleansRuntime 1.1.1
When paket.lock is created it looks like this:
Microsoft.Orleans.Core (1.1.1)
Newtonsoft.Json (>= 6.0.8)
Microsoft.Orleans.CounterControl (1.1.1)
Microsoft.Orleans.Core** (>= 1.1.1)**
Microsoft.Orleans.OrleansRuntime** (>= 1.1.1)**
Microsoft.Orleans.OrleansRuntime (1.1.1)
Microsoft.Orleans.Core** (>= 1.1.1)**
All dependencies are more permissive that is specified. I understand that these dependencies ranges are coming from nugets but I think they should be overridden in lock file. This will allow us to force users to use specific version of transitive dependencies
The text was updated successfully, but these errors were encountered: