-
Notifications
You must be signed in to change notification settings - Fork 903
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
installation/setup: run choco once to initialize the config file #1401
Comments
And here's the output:
|
@KirillOsenkov thanks for adding this. Adding to backlog. |
ferventcoder
changed the title
Consider initializing the config file when Chocolatey gets installed
installation/setup: run choco once to initialize the config file
Nov 3, 2017
gep13
added a commit
to gep13/choco
that referenced
this issue
Feb 22, 2018
- This ensures that all necessary setup is completed - Ready for further execution
gep13
added a commit
to gep13/choco
that referenced
this issue
Feb 22, 2018
- This ensures that all necessary setup is completed - Ready for further execution
gep13
added a commit
to gep13/choco
that referenced
this issue
Feb 22, 2018
- This ensures that all necessary setup is completed - Ready for further execution
ferventcoder
added a commit
that referenced
this issue
Feb 22, 2018
(GH-1401) Added initial call to Chocolatey after installation
Merged into stable at 3cb969b - will be released in v0.10.9. |
ferventcoder
added a commit
to ferventcoder/choco
that referenced
this issue
Feb 23, 2018
* stable: (chocolateyGH-1401) Added initial call to Chocolatey after installation
ferventcoder
added a commit
that referenced
this issue
Apr 9, 2018
With Chocolatey v0.10.9 and #1401, we added a call to choco to initialize the config file during installation so that it was generated during and administrative run. That was done in commit 35add3b. A call to choco with no switches results in an exit code of 1 instead of 0. Recently a call to choco to create the config file on install was added as the last step in installing Chocolatey. Unfortunately this resulted in an install or upgrade of Chocolatey resulting in a 1 instead of a 0. Call choco -v instead ot show the version, which exits with a 0 and also ensures the first time generation of the chocolatey.config file.
run PowerShell with admin rights |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What You Are Seeing?
First time after installing Chocolatey as admin, I start a non-admin command prompt, run
choco pack
and see this error:What is Expected?
It should work fine (whatever Chocolatey wants to write to ProgramData needs to be written at install time). Alternatively, consider saving the config file to LocalAppData (this doesn't need admin permissions to write, and is generally a better thing to do. Program Data goes to one place, configs, logs etc. go to another).
Output Log
Unfortunately I didn't grab the output log other than the screenshot above. I tried a workaround (which is to run pack under admin, and that created the config file and I got unblocked).
The text was updated successfully, but these errors were encountered: