-
Notifications
You must be signed in to change notification settings - Fork 904
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
Package not reporting correctly when interrupted during installation #782
Comments
Duplicate of #198. Already fixed in 0.9.10 ( |
I take it back - it's in the current beta - 0.9.10-beta-20160531 - so you can run |
Perfect i've just installed the beta and it works. any idea on timeline before beta becomes production? |
the same/similar issue is present in chocolately 1.10 when upgrading packages and the process is interrupted . in my case steps to reproduce : |
Hello, same problem for me. If installation of a package is interrupted during download or while installer is running, chocolatey says package is installed. Chocolatey v1.1.0 |
What You Are Seeing?
When something interrupts chocolatey install. Say a computer is rebooted during the install of firefox. Chocolatey thinks that the application is installed and if you run a choco list -lo it will show up as installed. But the MSI has actually failed to install.. In order to install again you either need
What is Expected?
Some sort of checks (even if this has to be done in the package) to do a confirmation of successful installation.
How Did You Get This To Happen? (Steps to Reproduce)
choco install (any package really) and remove power during the installation. i believe other things can cause it but this is one thing i know causes issues.
Use Case this effects:
We use chocolatey with our private repo to install software via group policy scripts. sometimes these scripts get interrupted as they're running in the background without users being aware. Our scripts don't install with --force (as they would be installing every time the script runs) so it requires manual intervention
The text was updated successfully, but these errors were encountered: