Skip to content
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

Unpack the powershell files just before packaging up the nupkg (Installing chocolatey meta) #347

Closed
ferventcoder opened this issue Jun 30, 2015 · 4 comments

Comments

@ferventcoder
Copy link
Member

Right now choco requires a functioning .NET 4+ framework install to even install itself on a machine. During install It will attempt twice to install .NET 4.0 if there isn't a version present, but it may run into errors or require a reboot before it is ready to be used. Because of this folks run into what looks like a missing file chocolateyInstaller.psm1 during install, when it's actually the former reason. Without .NET 4.0, the files can't be unpacked from choco.

Unpacking those files in the nupkg will allow the errors to be more visible on a non-functioning .NET framework install versus something with a file missing.

This will technically allow choco to be installed without the framework installed properly, just not useful.

@ferventcoder
Copy link
Member Author

@elventear
Copy link

@ferventcoder I would like to provide any information that would help debugging the issues that I am seeing on ansible but there are a couple of issues.

The first is that it seems the error is actually an exception thrown inside your script and it is bubbling up to my powershell context, where I am running the ansible script, which does not allow me to capture the output for the chocolatey installation script.

The second issue is that if I login int the machine and run the same ansible script it succeeds.

Any ideas on what could I do to try to provide more information of my problem?

@ferventcoder
Copy link
Member Author

I noticed you mentioned WinRM memory issues. Take a look at #277

@ferventcoder
Copy link
Member Author

The first is that it seems the error is actually an exception thrown inside your script and it is bubbling up to my powershell context, where I am running the ansible script, which does not allow me to capture the output for the chocolatey installation script.

@elventear If you are installing to the default folder, go to c:\programdata\chocolatey\logs and you should find a log file with the details of the error.

@ferventcoder ferventcoder changed the title Unpack the powershell files just before packaging up the nupkg Unpack the powershell files just before packaging up the nupkg (Installing chocolatey meta) Jul 25, 2015
@ferventcoder ferventcoder self-assigned this Sep 18, 2015
ferventcoder added a commit that referenced this issue Sep 18, 2015
Right now choco requires a functioning .NET 4+ framework install to
even install itself on a machine. During install It will attempt twice
to install .NET 4.0 if there isn't a version present, but it may run
into errors or require a reboot before it is ready to be used. Because
of this folks run into what looks like a missing file
`chocolateyInstaller.psm1` during install, when it's actually the former
reason. Without .NET 4.0, the files can't be unpacked from choco.

Unpacking those files in the nupkg will allow the errors to be more
visible on a non-functioning .NET framework install versus something
with a file missing.

This allows choco to be installed without the framework installed
properly, just not able to be used.
ferventcoder added a commit that referenced this issue Sep 18, 2015
* stable:
  (GH-177) Warn when admin not running elevated.
  (GH-347) Unpack choco files prior to nuget pack
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants