-
Notifications
You must be signed in to change notification settings - Fork 905
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
Empty $env:ChocolateyToolsLocation combine error #756
Comments
after doing the above, I noticed 7zip wasn't in my
something's definitely amiss in the install/upgrade process :( |
I noticed the
|
At least #198 works as advertised! |
no, once pending yanks a package, it's gone. |
It means incomplete install. |
ah. yes now |
The pending warning was just it telling you it was pulling the package... it happens on the first command that pending packages are found on. I think I know where this is. |
Related to #689. |
chocolatey.0.9.10-beta-20160530.nupkg.zip Rename to .nupkg. Let me know if this works. |
Guard against a non-initialized environment variable. ChocolateyToolsLocation may not be set yet, so guard against the value being null prior to attempting to combine the value's path with another item.
* stable: (GH-772) Uninstall-ChocolateyEnvironmentVariable (GH-765) Updates for Get-FtpFile (GH-697) Allow for ignored arguments (maint) miscellaneous PS fixes (GH-713) Rename Get-ProcessorBits Get-OSArchitectureWidth (GH-527) Url is optional (GH-697) Update Generated Documentation (GH-697) Update Code With Documentation (GH-697) Generate Documentation Automatically (GH-697) Update Current Docs for Generator (GH-697) rename CommandsSources to CommandsSource (GH-697) add current helpers/commands (maint) remove magic string environment vars (GH-756) Empty $env:ChocolateyToolsLocation combine error (GH-689) Report install work w/non-POSH pkgs
This affects all actions including upgrade in the
0.9.10-beta1-20160530
beta (yanked).What You Are Seeing?
Error while trying to upgrade a package during
cup all
. Never had issues with this previouslyWhat is Expected?
Package should update w/o issues
How Did You Get This To Happen? (Steps to Reproduce)
Ran
cup all -y -pre
which hit a different package each time (first time and when i ran with--debug --verbose
and attempted to upgrade it.Output Log
The text was updated successfully, but these errors were encountered: