(ruby2.devkit) Install script for ruby2.devkit getting errors about chocolatey-packages

[cmhamm]

Nope, I think I was wrong. $devKitInstallDir does seem to be pointed at $env:systemroot\tools, which makes line 89 correct.

However, looking over the script running order, it looks like it cleans out the contents of that folder, then downloads and extracts from 'http://cdn.rubyinstaller.org/archives/devkits/DevKit-mingw64-64-4.7.2-20130224-1432-sfx.exe'

Running and monitoring the installer, it looks like it's trying to run lines 90-91 before the other process has had a chance to re-download the archive that contains dk.rb.

Again, not fully understanding the entire Chocolatey process, is there a way to ensure that download has completed before running lines 90-91?

[ferventcoder]

@cmhamm perhaps you can help by specifically linking to the line numbers? https://github.com/ferventcoder/chocolatey-packages/blob/master/manual/ruby2.devkit/tools/chocolateyInstall.ps1#L67-L91

As in what process has had a change to redownload the archive?

[cmhamm]

Line 67 is "Start-Process "7za" -ArgumentList "x -o"$devKitInstallDir" -y "$file"" -Wait"

It looks like, at least on my machine, it's not waiting. I'm getting an admin prompt, I believe for the 7z executable, and it goes right onto the next process. I'm going to try to debug chocolatey...

[cmhamm]

Sorry - I have lots of experience in IT, but I am not a seasoned coder... Never even knew that line numbers could be linked.

I'm not sure what you're asking about what process has had a change. When I run the chocolatey installer, it tries to clear out the DevKit2 folder each time the installer script is run. It does successfully re-extract the archive after it runs, but it's definitely not waiting for the Start-Process to complete before moving on.

On my system, adding -NoNewWindow to the end of the Start-Process cmdlet seems to make it behave properly. What I'm not completely sure about is whether or not that would cause other problems in the script.

[cmhamm]

I don't know how to properly test the installer if I changed line 67 to:

Start-Process "7za" -ArgumentList "x -o`"$devKitInstallDir`" -y `"$file`"" -Wait -NoNewWindow

but I think that would resolve at least my problem. Also there are two other reports that I could find on the Internet of people having the same error. It's possible that it's because of one of the thousands of things I've done to my computer. 😄

[ferventcoder]

PowerShell v3?

[cmhamm]

I'm using PowerShell 5 on Windows 8.1.

[ferventcoder]

Weird that the no wait bug is back. It was in POSH v3 as well. See chocolatey-archive/chocolatey#516 for details.

[cmhamm]

I can't say for certain that it is the exact same bug, but it is the same behavior. Worth noting, though, that I did try running Chocolatey from within a PowerShell window vs. running from a command window, and it still did not work correctly.

[thj-dk]

I'm having the same problem on Windows 10. Did you solve it?

[falken]

Still having this problem when launching from Ansible. Has there been any progress?

[ferventcoder]

@thj-dk @falken What versions of Chocolatey and PowerShell do you have?

[falken]

Chocolatey: 0.9.10.3
Powershell: 3.0
Ansible: 1.9.1

We found that it worked fine if we set the "chocolateyUseWindowsCompression" env variable to true. Otherwise it attempted to run the chocolateyInstall.ps1 file before it was extracted.

[ferventcoder]

Now that Choco uses 7z.exe (full) plus we've changed up the code for this in Chocolatey, I'm not sure this is still an issue. If you find it is, please feel free to comment.

@falken If you are still seeing the same issue, please file an issue on https://github.com/chocolatey/choco

[falken]

We are still experiencing the problem. It seems to only occur when the choco script is run through ansible. Ansible runs choco.exe install -dv -y ruby2.devkit -y --x86 -version 4.7.2.2013022402 which fails to unzip all of the files. When running the command directly on the machine it succeeds. The only difference I can see is that the package is launching a second shell window that runs 7za.exe. I'm not sure why it would need to open a second shell to do that.