## Where communities thrive

• Join over 1.5M+ people
• Join over 100K+ communities
• Free without limits
##### Activity
Tunisiano18
@tunisiano187
Hello everyone, Does anyone as a solution to pin package version with the chocolatey's module for puppet in a manifest?
Thank you
Kevin Weinrich
@kwein1

I now have choco working via DSC for packages that are stored in Chocolatey's public repo. And I have the ORDChoco Source set up via DSC. When I log in to the remote server, I can do this:

 choco list -source ORDChoco
Chocolatey v0.10.15
sccm 0.1.0.20210106
1 packages found.

That was created by the following DSCWorkshop-style configuration:

ChocolateyPackages:
Software:
Ensure: Present
Sources:
Name: ORDChoco
Ensure: Present
Source: '\\A\chiz$\software installs and downloads\ChocolateyPackages' Features: Name: useFipsCompliantChecksums Ensure: Present Packages: - Name: sccm Ensure: Present ChocolateyOptions: Source: ORDChoco The one thing I still can't do is actually install my custom sccm package from ORDChoco. Am I getting hit with permissions, since I'm doing a DSC push from server A to B, and ORDChoco is on A? Is it because the account (SYSTEM, I guess?) that DSC is using can't access the share on A from B? Here's the peccant part of my DSC push: VERBOSE: [B]: [[ChocolateyPackage]Chocolatey_sccm::[ChocolateyPackages]ChocolateyPackages] Installing the following packages: VERBOSE: [B]: [[ChocolateyPackage]Chocolatey_sccm::[ChocolateyPackages]ChocolateyPackages] sccm VERBOSE: [B]: [[ChocolateyPackage]Chocolatey_sccm::[ChocolateyPackages]ChocolateyPackages] By installing you accept licenses for the packages. VERBOSE: [B]: [[ChocolateyPackage]Chocolatey_sccm::[ChocolateyPackages]ChocolateyPackages] sccm not installed. The package was not found with the source(s) listed. VERBOSE: [B]: [[ChocolateyPackage]Chocolatey_sccm::[ChocolateyPackages]ChocolateyPackages] Source(s): '\\A\chiz$\software installs and downloads\ChocolateyPackages'
@pauby
@tunisiano187 I'd use an exec for that and maybe an unless or an onlyif if it's not been pinned (run choco pin and parse it) to be idempotent.

The one thing I still can't do is actually install my custom sccm package from ORDChoco. Am I getting hit with permissions, since I'm doing a DSC push from server A to B, and ORDChoco is on A? Is it because the account (SYSTEM, I guess?) that DSC is using can't access the share on A from B?

You'll need to make sure B$(dollar is important) has access to the share. Kevin Weinrich @kwein1 @pauby I don't know what B$ is - do you mean the server name followed by a $? As a userid? Is there a better way to do this - to push the install file from A to B (via DSC somehow), and then install it locally on B via DSC? Paul Broadwith @pauby @pauby I don't know what B$ is - do you mean the server name followed by a $? As a userid? Yeah, the server name. Is there a better way to do this - to push the install file from A to B (via DSC somehow), and then install it locally on B via DSC? You could do it that way, but then you may have to update all of your packages that are using it. If you want to use file shares with authorisation this is the way it needs to be done unfortunately. This is why we recommend you use a repository manager. Kevin Weinrich @kwein1 I was able to get the package install to work after changing the permissions on the Source share, as @pauby indicated - add B$ to NTFS permissions. Works great!
Kevin Weinrich
@kwein1

Now I'm working on my 2nd custom package. This one fails, which is probably due to something I'm not doing right in constructing the package. But when I look for details on precisely WHAT went wrong with the installation, I just get "See the log for details...". The log just says

2021-01-15 15:04:12,065 1316 [ERROR] - ERROR: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The operation completed successfully.
2021-01-15 15:04:12,065 1316 [DEBUG] - Calling command ['"C:\Windows\System32\shutdown.exe" /a']
2021-01-15 15:04:12,174 1316 [DEBUG] - Command ['"C:\Windows\System32\shutdown.exe" /a'] exited with '1116'

I just don't see what it didn't like. Is there any way to get further debugging info about why it blows up? Or how can I manually walk through the package installation?

Note: In my chocolateyinstall.ps1, I do a "reg import ..." command which IS working. So I'm pretty sure it's the "Install-ChocolateyInstallPackage ..." command that's failing.

Kevin Weinrich
@kwein1
It appears that if I manually do:
setup.exe /s /v/qn
from the chocolatey package folder on the target server, it works. But
cinst bigfix -s ordchoco
still doesn't. How can I see what command line choco is actually using to try to run the setup.exe? (As I understand, it's using my chocolateyinstall.ps1 to call Install-ChocolateyInstallPackage, and the magic happens inside there)
Sathish
@satheeshsoft
Previously created chocolatey package working fine. The same code i used in new package but some changes in install file name and descriptions. The new package created with cpack command but not installing it, install failed. https://github.com/satheeshsoft/Soft-Cleaner-CY can you say what is missing here?
@pauby
@kwein1 Do you get any more info when adding -vd to the choco command line?
5 replies
@satheeshsoft Have you looked at the gist? The error is on this line.
VoomDev
@VoomDev
Is it possible to install choco on mac?
daebenji
@daebenji
VoomDev
@VoomDev
ok sorry
but is it possible to run choco on mac
daebenji
@daebenji
why would you need to to use choco on mac? they have homebrew and choco is trying to automate the installation of windows packages...
@pauby
@VoomDev Chocolatey is the package manager for Windows. There is Homebrew on Mac.
@pauby
@satheeshsoft The specific error is at these lines - it can't find the file.
Sathish
@satheeshsoft
@pauby got it, the directory name should be same name!
@pauby
@satheeshsoft :+1:
Sathish
@satheeshsoft
again some doubts
the app directory should be inside chocolatey directory?
sorry i forgot can you explain how to overcome the error
@pauby
Sathish
@satheeshsoft
no
@pauby
@satheeshsoft Then that would be my suggestion to allow you to troubleshoot the issue.
Sathish
@satheeshsoft
i created now but cinst not working message showing 3 attempts reached
created i think it may works fine, here checking max attempts reached
@pauby
@satheeshsoft Are you testing this in the Chocolatey Test Environment?
Sathish
@satheeshsoft
its difficult to understand, now created the pack
test environment difficult to understand & time taking
if the test environment automated its fair (like very few user inputs & also it works for the user demand without asking to user)
just saying a suggession
@pauby thanking to you
Sathish
@satheeshsoft
i used the same method in my software
Anonymous Planet
@AnonymousPlanet
Hi @pauby :) Concerning Issue chocolatey/chocolatey.org#687 about Tor Exit nodes. I just tested from about 10 various exit nodes. It's still 403 forbidden on the API no matter what.
2 replies
Anonymous Planet
@AnonymousPlanet
Also tested after resolving hCaptchas on Browser (using same exit nodes) and still forbidden unfortunately.
(hCaptchas are not required on the chocolatey.org website from a Tor Browser but are required when accessing the API). So there is no issue accessing the website in itself from Tor. Just the API URL.
Martin Bergman
@misse
Hello! I work at Electronic arts, managing an internal service that caches chocolatey (among other things) and starting today we're getting HTTP response 403 when trying to reach chocolatey. I've created a support ticket for this, but a colleague suggested I'd reach out here. Anyone up for a chat about why this happened and what we can do to get unblocked?