-
Notifications
You must be signed in to change notification settings - Fork 100
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
Source
option not working as expected
#44
Comments
When specifying a source, Chocolatey should only look at that source. @simondel I think the provider here may not be passing through quite correctly. I'm guessing the following may work as a workaround for now: cChocoPackageInstaller HipChat
{
Name = 'hipchat'
Source = 'https://our.private.repo.net/nuget'
DependsOn = "[cChocoInstaller]InstallChocolatey", "[cChocoSource]Privaterepo"
} |
If not, it's likely a bug in this provider. |
Thanks for the quick response! I initially used your suggestion and then moved to a cChocoSource resource when that didn't work (and because I was specifying the url more than once in my DSC config). |
Yup. the issue is that instead of running the install passing through the -source command to chocolatey it is just adding the source to chocolatey. |
Indeed, the code mentioned above is incorrect. If #50 get's merged I'll continue work on this, seems like a rather easy thing to fix. |
Is there a timeline for getting this resolved, its still broken? |
This is still not yet resolved, however I'm going to set it up for being fixed in 2.4.0. |
Let us know when you have a fix for this, we're experiencing the same issue when trying to install packages from various sources, internal and external. Working around it by adding the sources to the config using cChocoSource but would be nice if this worked as expected |
As an aside, I found that as long as my package was not named exactly the same as a public one, it works fine. |
This looks to be fixed with #84. |
The Source parameter for the cChocoPackageInstaller DSC Resource is not used by the choco install and choco upgrade commands. This commit rectifies this issue.
The Source parameter for the cChocoPackageInstaller DSC Resource is not used by the choco install and choco upgrade commands so packages get installed and upgraded from the central chocolatey repository instead of the url specified in the Source parameter. This commit rectifies this issue.
(GH-44) Pass the Source correctly to choco
This is now fixed and will go into the next release of cChoco |
* development: (GH-71) Implemented cChocoFeature (GH-87) Moved to using reduced output (maint) formatting (GH-70) Apply Apache v2 Licensing (GH-85) Pass the source to cChocoPackageInstallerSet correctly (GH-44) Pass the Source to choco correctly Added version to example (GH-77) Push to gallery on new tags (maint) formatting (GH-72) PowerShell scripts in format for signing
…ages_for_faster_run * development: (chocolateyGH-87) Moved to using reduced output (maint) formatting (chocolateyGH-70) Apply Apache v2 Licensing (chocolateyGH-85) Pass the source to cChocoPackageInstallerSet correctly (chocolateyGH-44) Pass the Source to choco correctly Added version to example (chocolateyGH-77) Push to gallery on new tags (maint) formatting (chocolateyGH-72) PowerShell scripts in format for signing # Conflicts: # DSCResources/cChocoPackageInstall/cChocoPackageInstall.psm1
I'm having some issues with the
Source
option in thecChocoPackageInstaller
. We have a private Chocolatey repository which we use for some packages. I'm working a package right now which has the same name as a public package, my config is like this:During testing our private hipchat package had a lower version (0.0.6) than the public package (2.2.1164) and when applying the DCS configuration, the public package was installed instead of our private package.
I would expect that our private package would be installed here since the command
does install our private version.
The text was updated successfully, but these errors were encountered: