``` source https://www.nuget.org/api/v2/ nuget Rx-Interfaces ~> 2.2 nuget NUnit ~> 2.6 ``` ``` NUGET remote: https://www.nuget.org/api/v2 specs: NUnit (2.6.1) Rx-Interfaces (2.2.2) ``` ``` bash $ paket outdated Paket version 0.17.16.0 found: paket.dependencies Resolving packages: - fetching versions for NUnit - exploring NUnit 2.6.3 - fetching versions for Rx-Interfaces - exploring Rx-Interfaces 2.2.5 Outdated packages found: * NUnit 2.6.1 -> 2.6.3 * Rx-Interfaces 2.2.2 -> 2.2.5 2 seconds - ready. ``` Wrong casing, `nunit`: ``` bash $ paket update nuget nunit Paket version 0.17.16.0 found: paket.dependencies Resolving packages: - exploring NUnit 2.6.1 - exploring Rx-Interfaces 2.2.2 Locked version resolutions written to paket.lock 3 seconds - ready. ``` Correct casing, `NUnit`: ``` bash $ paket update nuget NUnit Paket version 0.17.16.0 found: paket.dependencies Resolving packages: - fetching versions for NUnit - exploring NUnit 2.6.3 - exploring Rx-Interfaces 2.2.2 Locked version resolutions written to paket.lock NUnit 2.6.3 unzipped to packages\NUnit 2 seconds - ready. ``` `nuget.exe` doesn't care about casing, but we apparently do: ``` bash $ nuget install nunit Installing 'NUnit 2.6.3'. Successfully installed 'NUnit 2.6.3'. ```
Activity
agross commentedon Dec 6, 2014
BTW,
paket add nuget machine.specificationsworks as well. We shouldpaket add nuget <name>andpaket update nuget <name>forki commentedon Dec 6, 2014
Yes there are still some places where have to use the corrected version name.
Fix casing issue in selective update - fixes #429
Merge pull request #434 from fsprojects/Casing