Ryan Trinkle writes:
> I would strongly urge that any new tarballs be released under new names,
> and that the old tarballs be kept in place. Changing existing tarball URLs
> silently causes breakage for Nix, and, I would imagine, for any other build
> systems that are
Phyx writes:
> We have discussed a few options on what to do, but haven't gotten a
> conclusion/concensus yet.
>
Tamar and I have discussed this on IRC in the passed. I tend to agree
that we will need to, at the very least, put out a new 8.0.2. I'm not
sure about 7.10.
skell.org] *On Behalf Of
>> *Sebastian
>> Graf
>> *Sent:* 04 April 2017 09:12
>> *To:* ghc-devs <ghc-devs@haskell.org>
>> *Subject:* Windows 10 Creators Update will break GHC (Was FW: GHC on
>> Windows 10 15019+)
>>
>>
>>
>> Hi,
>
Help would be fantastic. Phyx, Ben, etc: do we have a plan?
>
>
>
> Simon
>
>
>
> *From:* ghc-devs [mailto:ghc-devs-boun...@haskell.org] *On Behalf Of
> *Sebastian
> Graf
> *Sent:* 04 April 2017 09:12
> *To:* ghc-devs <ghc-devs@haskell.org>
> *Subje
] On Behalf Of Sebastian Graf
Sent: 04 April 2017 09:12
To: ghc-devs <ghc-devs@haskell.org>
Subject: Windows 10 Creators Update will break GHC (Was FW: GHC on Windows 10
15019+)
Hi,
when the Creators Update finally hits Windows 10 stable on April 11th (next
week), every currently availab
Also note that a minimal patch already exists which will ship in GHC 8.2:
https://git.haskell.org/ghc.git/commitdiff/018ac7f4b2f7345e28d21fb1f99b44dbc79f6e85
It's 'just' a matter of packaging that up in a hotfix.
On Tue, Apr 4, 2017 at 10:12 AM, Sebastian Graf wrote:
> Hi,
Hi,
when the Creators Update finally hits Windows 10 stable on April 11th (next
week), every currently available GHC will be broken by it.
See [1] for the previous discussion, [2] and [3] for the tickets discussing
this. From what I read on the GHC 8.2 status wiki page, there might be an