[Issue] Failed to Install-Package with `-RequiredVersion` option

[jianyunt]

[Issue] Failed to Install-Package with `-RequiredVersion` option

[ethanbergstrom]

Hey @dougpuob,

Glad to hear ChocolateyGet is making life easier for you!

The issue you're describing seems to be more of a quirk with choco itself, rather than ChocolateyGet.

If you run Install-Package or Find-Package with the -debug flag, it will actually list out the command line arguments passed to choco.exe. For ninja 1.10.2, that's choco.exe search ninja --version 1.10.2 --source Chocolatey which also returns no results.

From what I can find, this seems to be related to this choco issue that was opened a while ago, but is now closed and doesn't look like anyone is going to fix it. It looks like most folks are working around the problem by passing the --exact flag to choco, which skips package description text search and assumes your search text is the exact package name you want.

Since ChocolateyGet is going to return whatever choco.exe does, what you'd probably need to run is:
Install-Package ninja -ProviderName ChocolateyGet -RequiredVersion 1.10.2 -AdditionalArguments '--exact'

Hope that works for you!

[ethanbergstrom]

Actually, thinking about this a little more, I think I could make that experience better: to assume --exact behavior if package name and required version are specified.

[ethanbergstrom]

Will need to downgrade the version of the choco Native API DLL to version 0.10.13 due to a different choco issue that won't be fixed until the 0.10.16 API is released in order for the exact behavior to work with the OneGet MinimumVersion\ MaximumVersion\ AllVersions flags.

[ethanbergstrom]

@dougpuob,

ChocolateyGet v2.1.0 is now out on PSGallery, and my tests indicate it now works without having to sometimes pass -AdditionalArguments '--exact' depending on how many results match in the repository.

This does however, introduce a possible new with issue with -MaximumVersion and -AllVersion flags that is in turn caused by a defect in Chocolatey itself, but there are a few workarounds available.

Please see the updated documentation in the readme for more details.