Skip to content

Invalid flag name: "bytestring--lt-0_10_4" #150

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
bwbaugh opened this issue Aug 14, 2017 · 2 comments
Closed

Invalid flag name: "bytestring--lt-0_10_4" #150

bwbaugh opened this issue Aug 14, 2017 · 2 comments

Comments

@bwbaugh
Copy link

bwbaugh commented Aug 14, 2017

While trying to generate a stack.yaml for jtdaugherty/tart, I ran into the following error about the bytestring--lt-0_10_4 flag:

$ stack init --solver --resolver=nightly
Looking for .cabal or package.yaml files to use to init the project.
Using cabal packages:
- tart.cabal

Selected resolver: nightly-2017-08-14
Selected resolver: nightly-2017-08-14
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\""
@hvr
Copy link
Collaborator

hvr commented Aug 14, 2017

I'm afraid I'll have to redirect you to the Stack issue tracker, as this is a bug in Stack. The package works perfectly fine with cabal & hackage.

@hvr hvr closed this as completed Aug 14, 2017
tfausak added a commit to tfausak/cassava that referenced this issue Sep 8, 2017
@tfausak
Use more compatible flag name
1f66af2 
This flag name was changed without comment in 6e1ff78. It has caused a few problems:

- commercialhaskell/stack#3345
- commercialhaskell/stackage#2755
- commercialhaskell/stackage#2759
- commercialhaskell/stackage#2842
- haskell/cabal#4686
- haskell-hvr#150

Those problems either caused or accelerated some (attempted) changes in Cabal:

- haskell/cabal#4654
- haskell/cabal#4687
- haskell/cabal#4696

Those problems also caused a change in Stack:

- commercialhaskell/stack#3349

In short: Cabal never had any trouble with this. Stack did. The current master version of Stack can handle flags like this, but no released versions of it can. It's not clear when the next version of Stack will be released. In the meantime, no Stack users can use this package. This commit changes the offending flag to something that Stack can handle. By using a flag that Stack can handle, Stack users can once again use this package, and it can return to Stackage. There are no apparent downsides to using a more compatible flag name.
@johnmendonca
Copy link

stack upgrade should fix this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@johnmendonca @hvr @bwbaugh