Stack build error: AesonException

[kgadek]

I believe there's problem with recent nightlies.

resolver: nightly-2017-08-14
packages: 
- '.'
flags: {}
extra-package-dbs: []

Downloaded nightly-2017-08-14 build plan.
AesonException "Error in $.packages.cassava.constraints.flags['bytestring--lt-0_10_4']: Invalid flag name: \"bytestring--lt-0_10_4\""

However, if I use nightly-2017-08-12 then everything works. Or is it stack problem? (1.5.1 x86_64 hpack-0.17.1)

---

The only mention of anything related to error message is build-constraints.yaml:3375:

# Package flags are applied to individual packages, and override the values of
# global-flags
package-flags:

    # …snip to line 3375…

    cassava:
        pre-bytestring-0-10-4: false

I looked into my nightly-2017-08-14.yaml and replaced bytestring--lt-0_10_4: false with pre-bytestring-0-10-4: false. That fixed the problem. Changing bytestring--lt-0_10_4: false → bytestring-lt-0_10_4: false also solves the initial problem.

---

I've also found that stack with --flag cassava:-bytestring--lt-0_10_4 yields:

option --flag: Invalid flag name: bytestring--lt-0_10_4

---

stack from HEAD fixes the problem and — per discussion — it appears that this will get fixed soon. Not sure if I should close the ticket

[snoyberg]

Thanks for opening the ticket. The next nightly release will fix this by moving back to the older cassava. And as you noted, Stack's HEAD fixes this by doing no flag name validation (yay?).

[austinvhuang]

The issue seems to have returned, possibly with a newer cassava in a more recent LTS:

$ stack new ghc-memory simple
stack new ghc-memory simple
Downloading template "simple" to create project "ghc-memory" in ghc-memory/ ...

The following parameters were needed by the template but not provided: author-email, author-name, category, copyright, github-username
You can provide them in /Users/huanga13/.stack/config.yaml, like this:
templates:
  params:
    author-email: value
    author-name: value
    category: value
    copyright: value
    github-username: value
Or you can pass each one as parameters like this:
stack new ghc-memory simple -p "author-email:value" -p "author-name:value" -p "category:value" -p "copyright:value" -p "github-username:value"

Looking for .cabal or package.yaml files to use to init the project.
Using cabal packages:
- ghc-memory/ghc-memory.cabal

Selecting the best among 12 snapshots...

Downloaded lts-10.0 build plan.
AesonException "Error in $.packages.cassava.constraints.flags['bytestring--lt-0_10_4']: Invalid flag name: \"bytestring--lt-0_10_4\""

[snoyberg]

Please upgrade to Stack 1.6.1 with `stack upgrade`

…

On Thu, Dec 21, 2017 at 5:02 PM, Austin Huang ***@***.***> wrote: The issue seems to have returned, possibly with a newer cassava in a more recent LTS: $ stack new ghc-memory simple stack new ghc-memory simple Downloading template "simple" to create project "ghc-memory" in ghc-memory/ ... The following parameters were needed by the template but not provided: author-email, author-name, category, copyright, github-username You can provide them in /Users/huanga13/.stack/config.yaml, like this: templates: params: author-email: value author-name: value category: value copyright: value github-username: value Or you can pass each one as parameters like this: stack new ghc-memory simple -p "author-email:value" -p "author-name:value" -p "category:value" -p "copyright:value" -p "github-username:value" Looking for .cabal or package.yaml files to use to init the project. Using cabal packages: - ghc-memory/ghc-memory.cabal Selecting the best among 12 snapshots... Downloaded lts-10.0 build plan. AesonException "Error in $.packages.cassava.constraints.flags['bytestring--lt-0_10_4']: Invalid flag name: \"bytestring--lt-0_10_4\"" — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#2759 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADBBzJ0u6P3Dx6laydXgGG2v7D1ksQHks5tCnL7gaJpZM4O3ExP> .

[austinvhuang]

Resolved thanks.

[denisgrib]

On ubuntu also after
stack upgrade

stack setup         
                                                                                                                                                                                   
Run from outside a project, using implicit global project config
Using resolver: lts-10.5 from implicit global project's config file: /home/xxx/.stack/global-project/stack.yaml
Downloaded lts-10.5 build plan.    
AesonException "Invalid flag name: \"bytestring--lt-0_10_4\""

[bergmark]

@Spaceblock you probably have the old stack in your PATH, the new one should be in ~/.local/bin.

[denisgrib]

@bergmark

> $ where stack                                                                                                                                                                                            
/usr/bin/stack

> $ /usr/bin/stack --version                                                                                                                                                                               
Version 0.1.10.0 x86_64

> $ /usr/bin/stack upgrade                                                                                                                                                                                 
Fetched package index.                                                                                    
Populated index cache.    
Could not parse '/tmp/stack-upgrade9644/stack-1.6.5/stack.yaml':
AesonException "failed to parse field 'extra-deps': when expecting a PackageIdentifier, encountered Object instead"
See https://github.com/commercialhaskell/stack/blob/release/doc/yaml_configuration.md.

[bergmark]

Right, that seems to verify the path issue, 0.1.10.0 is too old.

[bergmark]

Sorry, I misread the error. I'm not sure how to resolve that one... But you could always get the binary as described in https://docs.haskellstack.org/en/stable/README/

[denisgrib]

@bergmark thx, installed from curl -sSL https://get.haskellstack.org/ | sh
in ubuntu too old package.

[QLaille]

Still an issue for me, even after forcing the reinstallation with curl -sSL https://get.haskellstack.org/ | sh -s - -f
Same setup, and same issues as @Spaceblock , I'm kinda lost now

[bergmark]

@QLaille looks like the old stack is still in your PATH, is the new one in ~./local/bin?

[QLaille]

@bergmark Negative, there's nothing related to stack in there, what should I do ?

[QLaille]

After trying to move stack in ~/.local/bin , it appears to be quite the same, not sure if I'm doing it wrong

[juhp]

What does stack --version say now?

[QLaille]

After re-installing stack via cabal install stack it was successfully installed on my ~/.local/bin folder, I forgot to answer back !

EDIT: What I conclude is that trying to install stack via the ubuntu package or manually via the command line, stack keeps being installed in the /usr/bin/ path, while cabal itself could install it to the appropriated folder, i'm quite clueless about what I did and if something is wrong in the end.