We are definitely leaning the same way!  In fact I'm building the binaries 
right now.

> On Dec 6, 2017, at 8:30 AM, Neil Mitchell <[email protected]> wrote:
> 
> Given these issues, all released versions of Stack are unable to use
> Stackage nightly. Can I suggest a swift Stack release? It's certainly
> going to be a better experience than doesn't work at all, even if it
> has RC1 style bugs left in it. FWIW, all my nightly builds just broke.
> 
> Thanks, Neil
> 
> 
> On Tue, Dec 5, 2017 at 7:56 PM, Mark Fine <[email protected]> wrote:
>> Yes! I ran into the problem before the issue turned up (I'm on 8.2.2). The
>> versioning and compatibility management around these cabal updates continues
>> to be... interesting.
>> 
>> Mark
>> 
>> On Mon, Dec 4, 2017 at 9:59 PM, Michael Snoyman <[email protected]>
>> wrote:
>>> 
>>> Looks like you're running into
>>> https://github.com/commercialhaskell/stack/issues/3624. Since newer versions
>>> of GHC are pulling in cabal files in the 2.0 format, versions of Stack
>>> without the Cabal-2.0 library (meaning: everything before 1.6) aren't
>>> supported. I've requested that such cabal files be held off in active use
>>> until tooling has a chance to upgrade, but that request was denied.
>>> 
>>> On the bright side: Stack 1.6 is _also_ less eager about parsing cabal
>>> files it doesn't need, so this problem will be less of a pain in the future.
>>> See: https://github.com/commercialhaskell/stack/issues/3396.
>>> 
>>> On Tue, Dec 5, 2017 at 2:12 AM, Mark Fine <[email protected]> wrote:
>>>> 
>>>> I now run into problems without it!
>>>> 
>>>> $ docker build --no-cache .
>>>> Sending build context to Docker daemon  4.096kB
>>>> Step 1/5 : FROM haskell:8.2.1
>>>> ---> 5c2a170680fe
>>>> Step 2/5 : WORKDIR /app
>>>> ---> c8de7a174535
>>>> Removing intermediate container 6a672c3b44b7
>>>> Step 3/5 : COPY . /app
>>>> ---> 37588f4c6322
>>>> Step 4/5 : RUN stack --version
>>>> ---> Running in ddcd9ccdaf20
>>>> Version 1.5.1, Git revision 600c1f01435a10d127938709556c1682ecfd694e
>>>> (4861 commits) x86_64 hpack-0.17.1
>>>> ---> f79f9c618049
>>>> Removing intermediate container ddcd9ccdaf20
>>>> Step 5/5 : RUN stack build --only-dependencies
>>>> ---> Running in a1cb8152f248
>>>> Downloading nightly-2017-12-01 build plan ...
>>>> Downloaded nightly-2017-12-01 build plan.
>>>> Updating package index Hackage (mirrored at
>>>> https://s3.amazonaws.com/hackage.fpcomplete.com/) ...
>>>> Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
>>>> Downloading root
>>>> Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
>>>> Downloading timestamp
>>>> Downloading snapshot
>>>> Downloading mirrors
>>>> Cannot update index (no local copy)
>>>> Downloading index
>>>> Updated package list downloaded
>>>> Populating index cache ...
>>>> Populated index cache.
>>>> Unable to parse cabal file for integer-gmp-1.0.1.0: NoParse
>>>> "build-depends" 58
>>>> The command '/bin/sh -c stack build --only-dependencies' returned a
>>>> non-zero code: 1
>>>> 
>>>> Minimal files:
>>>> 
>>>> ==> Dockerfile <==
>>>> FROM haskell:8.2.1
>>>> 
>>>> WORKDIR /app
>>>> 
>>>> COPY . /app
>>>> 
>>>> RUN stack --version
>>>> 
>>>> RUN stack build --only-dependencies
>>>> ==> silly.cabal <==
>>>> name:                silly
>>>> version:             0.1.0
>>>> build-type:          Simple
>>>> cabal-version:       >= 1.22
>>>> 
>>>> library
>>>>  build-depends:     base >= 4.8 && < 5
>>>>  default-language:  Haskell2010
>>>> 
>>>> ==> stack.yaml <==
>>>> resolver: nightly-2017-12-01
>>>> packages:
>>>> - .
>>>> 
>>>> 
>>>> 
>>>> On Sat, Dec 2, 2017 at 1:54 PM, Emanuel Borsboom <[email protected]>
>>>> wrote:
>>>>> 
>>>>> I've cut the first stack-1.6.1 release candidate:
>>>>> https://github.com/commercialhaskell/stack/releases/tag/v1.6.0.20171202.
>>>>> Please give it a try!  I included 64-bit binaries for Linux, macOS, and
>>>>> Windows.  We'll plan on doing the full v1.6.1 release in around a week
>>>>> unless there are any show-stopping bugs.
>>>>> 
>>>>> If you do run into any trouble, please open an issue:
>>>>> https://github.com/commercialhaskell/stack/issues.
>>>>> 
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "haskell-stack" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to [email protected].
>>>>> To post to this group, send email to [email protected].
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/haskell-stack/5D85552F-B0F7-4E46-8930-6F465D8F79D8%40fpcomplete.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>> 
>>>> 
>>>> --
>>>> You received this message because you are subscribed to the Google Groups
>>>> "haskell-stack" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an
>>>> email to [email protected].
>>>> To post to this group, send email to [email protected].
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/haskell-stack/CANRZ_f%3Drs0nx0jtZVKMqwR_WHsa5x4zUtC__gJFfwoP6EwGAmA%40mail.gmail.com.
>>>> 
>>>> For more options, visit https://groups.google.com/d/optout.
>>> 
>>> 
>> 
>> --
>> You received this message because you are subscribed to the Google Groups
>> "haskell-stack" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> To post to this group, send email to [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/haskell-stack/CANRZ_fkeppUoLPKpNC8F%3DxNiHowZHpd4-kr0bf0JpXrXFYC-kQ%40mail.gmail.com.
>> 
>> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"haskell-stack" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/haskell-stack/4F23B535-858B-4D06-912A-7EF7A2071805%40fpcomplete.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to