Skip to content
This repository has been archived by the owner on Jun 21, 2022. It is now read-only.

Chocolatey Provider should return only one entry to Oneget's Install-Package #6

Open
JohnLudlow opened this issue Mar 4, 2016 · 4 comments

Comments

@JohnLudlow
Copy link

I tried to install VirtualBox using the Windows 10 PackageManagement Install-Package cmdlet, but got this error:

PS C:\WINDOWS\system32> install-package virtualbox
WARNING: 'virtualbox' matched package 'virtualbox/5.0.14.105127' from provider: 'Chocolatey', source 'chocolatey'
WARNING: 'virtualbox' matched package 'VirtualBox.ExtensionPack/5.0.14.105127' from provider: 'Chocolatey', source
'chocolatey'
install-package : Unable to install, multiple packages matched 'virtualbox'. Please specify an exact -Name and
-RequiredVersion.
At line:1 char:1
+ install-package virtualbox
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package], E
   xception
    + FullyQualifiedErrorId : DisambiguateForInstall,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage


PS C:\WINDOWS\system32>

Clearly, I want to install VirtualBox. I got around this by using Find-Package and piping into Install-Package, but this shouldn't really be necessary. I noticed similar issues with npm and 7zip.

I raised an issue on Oneget:OneGet/oneget#169. The folks over there feel that Chocolatey is returning multiple results in this situation when it should return one - most likely, the package that matched the name exactly.

@ferventcoder
Copy link
Contributor

I agree. The problem here is that we don't have a provider available yet for OneGet, so YMMV on whatever it is that you are using, likely the CTP built by MS in April 2014. I would suggest you use the official choco client for now and wait for us to announce official OneGet support (which we expect to have sometime this summer). We'll announce it in the newsletter. Thanks!

@JohnLudlow
Copy link
Author

Ok, will do

Waiting patiently....
Waiting patiently....
Waiting patiently....

Ready yet? ;P

Thanks!

PS: Do you want to close this issue or leave it open for now?

@ferventcoder
Copy link
Contributor

Let's keep it open in case other folks come across this issue. :)

@JohnLudlow
Copy link
Author

Sounds like a plan

Thanks again

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants