If disabled: # If the repo is not named chocolatey, use the repo name returned by the choco sources command If the public repo doesn't show here, or you see following the repo name, fix it like so: Assuming you're looking for a public package, you should see a chocolatey repository returned similar to the following (the URL is what's important here): chocolatey - | Priority 0|Bypass Proxy - False|Self-Service - False|Admin Only - False. This should list all repos configured on your system. If it still doesn't work but you've confirmed the package exists, make sure that you have the public repo configured (or internal repo if this is a non-public package, but obviously I won't have that URL here): choco sources
If you find the package here, try installing it with the command they give you (the package information page will include a copy/pastable installation command). Not everything has a Chocolatey package, they are often maintained by third-party volunteers. If you don't get any hits, double check the online portal that the package actually exists. If you get a response, double check the package name is correct for what you passed to choco list sometimes the package name might be different but still be tagged for the search term you used. Where packageName is the name of the package you want to install. If this doesn't work or you are using PowerShell as your CLI, then read on for some config troubleshooting steps.Ĭheck that the package exists in one of your configured repos: choco list packageName
Remove the single quotes and it should work. Most likely, it's because you're doing this from the Command Prompt, and wrapping the package name in single-quotes.
0 kommentar(er)
