-
Notifications
You must be signed in to change notification settings - Fork 25
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.
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
Support optparse-applicative 0.13 #52
Comments
It's actually unrelated to that particular PR, as far as I can tell. Unfortunately, travis doesn't know how to tell the difference between new issues that arise over time with existing stackage dependencies, and issues with the PR in question. |
Note that due to this revision I have temporarily removed angel from the Stackage nightly builds (which use optparse-applicative-0.13). I don't see why the upper bound was added, though. |
Double checking with @hvr, did you mean to put [1] http://hackage.haskell.org/package/angel-0.6.2/revisions/ |
@DanBurton I did mean to place <0.13 there, as I got this compile failure which I attributed to optparse-applicative-0.13 not reexporting
|
I tried to build
@DanBurton how |
@phadej I'm not quite sure how that happened. I'm able to reproduce the issue like so:
|
@hvr seems like it may be an easy workaround to avoid the bounds. Wouldn't you just explicitly import (<>) from Data.Monoid? |
@DanBurton The simplest explanation I can think of is the stackage nightly buildbot failed to re-check the build-status for |
@MichaelXavier yes, that would be the proper fix to make Btw, you also should add a lower bound on PS: In a few years, |
@hvr I just added a lower bound on optparse-applicative >= 0.12.0.0. On my own machine I set it to 0.13.0.0 and it seemed to work. Should I go ahead and release this or does someone want to do more testing? Also, let me know if you'd like commit bit on this project. I'm not actively using Angel, and people who are should have a greater say in how it goes forward. I'm basically just the janitor. |
@MichaelXavier I think you'll still have to import |
Motivated by commercialhaskell/stackage#2091
The text was updated successfully, but these errors were encountered: