-
Notifications
You must be signed in to change notification settings - Fork 846
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Error installing msys2 with stack 0.1.5.0 on Windows #1046
Comments
Does this happen deterministically? Or could this perhaps be a random On Fri, Sep 25, 2015, 12:39 AM Rolf Karp notifications@github.com wrote:
|
Yes, it always happens in the same spot. If I try to call stack setup again afterwards, I get this error:
This might be because some files in there have the "system file" attribute, so even Windows Explorer asks for confirmation before deleting them. Doing After I delete the directory, stack setup will again abort with the first error. If I try to call pacman myself afterwards, this happens:
|
I've just tried it again after deleting the msys2 folder and now it works, even though I got the original error just minutes ago. I guess the download of the git tar didn't work and they just fixed it? |
I saw this happen a couple times a while back, but haven't seen it since. |
Forgot to put this comment in earlier. Combining this with the fact that we're not even certain preinstalling git is a good idea (due to the CRLF issue), should we just skip that step in the setup process? |
+1 on skipping git. |
Cool. Probably no longer relevant, but I've been running
And then running
|
I'm going to guess this is a bug in MSYS2 itself, not in anything we're doing. It may be worth reporting upstream. |
:( IMO, MSYS2 is way too heavy to be isolating and using ourselves. It deserves to be installed by the end users. |
Hi there. I've just tested the latest stack. I would like to point out that the command @borsboom from my experience the "permission denied" issues are often solved by closing the Explorer. @3noch it may be heavy but it is very practical to have an all-in-one installation especially on Windows. |
Here's what worked for me:
After going through these steps and ensuring I had these "module" files in place, stack behaved as expected. Hope this helps others! |
This happens when I run
stack setup
on Windows:The text was updated successfully, but these errors were encountered: