process 1.6.0

[curtisalexander]

When will process 1.6.0 be released on stackage -- either nightly or an LTS release?

I ask because I have been trying to install stack on Windows and believe that the error I'm receiving was fixed by this PR.

I am quite new to Haskell and stack and thus may be completely misunderstanding how everything fits together.

As an alternative, I can open an issue over at the stack repo if this is the wrong place for my question.

[snoyberg]

The changes are already released, see the changelog at https://www.stackage.org/package/process. Because process is a wired in package, Stackage snapshots don't upgrade automatically. Can you open a Stack issue requesting that the Windows binaries be built with the newer process? I think there may also be some code changes necessary to make this all work.

…

On Thu, Apr 27, 2017, 2:33 AM Curtis Alexander ***@***.***> wrote: When will process 1.6.0 be release on stackage -- either nightly or an LTS release? I ask because I have been trying to install stack on Windows and believe that the error I'm receiving was fixed by this PR <#80>. I am quite new to Haskell and stack and thus may be completely misunderstanding how everything fits together. As an alternative, I can open an issue over at the stack repo if this is the wrong place for my question. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#95>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADBB35hr38eQIcf4ZXt9GgfIoUzVUGFks5rz9RAgaJpZM4NJjLO> .

[curtisalexander]

@snoyberg Thank you for the response. I did as you suggested -- here is the issue.

As I said in the issue I filed, I'll be glad to troubleshoot further if need be. If my issue is not related to process and version 1.6, then I'll be glad to split my issue into two - incorporating process 1.6 into the Windows binaries and a separate issue for the issue I'm facing.

[RyanGlScott]

process-1.6.0.0 has since been released, so I'll close this issue in favor of commercialhaskell/stack#3145.