You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I mentioned this before in April - chocolatey/choco#512. 0.9.10 just released today and folks are going to start reporting breakages even though we noted it in our release notes and tried to give plenty of notice to folks that it was coming (2 months notice in this case).
Here is the relevant portion of the ChangeLog (under breaking changes):
Exit with the same exit code as the software being installed - see #512
There are more exit codes from Chocolatey now that indicate success -0, 1605, 1614, 1641, and 3010. You may need to adjust anything you were using that would only check for 0 and nonzero.
If you need the previous behavior, be sure to disable the feature usePackageExitCodes or use the --ignore-package-exit-codes switch in your choco commands.
The text was updated successfully, but these errors were encountered:
ferventcoder
changed the title
Chocolatey 0.9.10 and exit codes
Chocolatey 0.9.10 and exit codes - reporting package install failures
Jun 17, 2016
ferventcoder
changed the title
Chocolatey 0.9.10 and exit codes - reporting package install failures
Chocolatey 0.9.10 and exit codes - Provider is now reporting successful package installs as failures
Jun 17, 2016
ferventcoder
changed the title
Chocolatey 0.9.10 and exit codes - Provider is now reporting successful package installs as failures
Chocolatey 0.9.10 and exit codes - Chocolatey Package Provider is now reporting successful package installs as failures
Jun 17, 2016
The workaround until the provider handles this correctly is listed above.
To reiterate:
If you need the previous behavior, be sure to disable the feature usePackageExitCodes or use the --ignore-package-exit-codes switch in your choco commands.
You can add this to install_options or set the feature.
It's preferred to set the feature. You can do that with this:
I mentioned this before in April - chocolatey/choco#512. 0.9.10 just released today and folks are going to start reporting breakages even though we noted it in our release notes and tried to give plenty of notice to folks that it was coming (2 months notice in this case).
Here is the relevant portion of the ChangeLog (under breaking changes):
The text was updated successfully, but these errors were encountered: