-
Notifications
You must be signed in to change notification settings - Fork 804
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
happy-2.0 #7520
Comments
Signed-off-by: Mihai Maruseac <[email protected]>
@sgraf812 : Looks like |
Can do! |
Thanks! That means in practice that you add yourself to the stackage/build-constraints.yaml Line 113 in 1def8db
(And of course add a line for happy-lib .)
|
I trust that the stackage curators know what that means and remove the upper bound again(?) Does stackage understand deprecated versions? I'm going to deprecate 2.0 in favour of 2.0.1 due to haskell/happy#303. |
Yes, they will when they can close this issue.
Stackage only has a single version of each package per snapshot, and by default the latest versions enter the nightly snapshot. So, once the bound |
I think this issue is only fixed after removing the |
That's true, reopening |
Okay it's "just me" hm: so actually config-value is not my package at all, I just added it to get copilot into Stackage... @glguy actually made a commit yesterday already: glguy/config-value@a5f7f92 so I guess we just need to wait or poke him for a release. |
FWIW, we aren't in a rush here. I don't think anyone is waiting for happy 2.0. I was just wondering if some step in the process was blocked on me without knowing |
I updated the bound on hackage |
I think now we are blocked on |
Fixed by |
Thank you! |
happy-2.0 (changelog) (Andreas Abel [email protected] @andreasabel) is out of bounds for:
happy-lib (not present) depended on by:
Will place an upper bound on
happy
The text was updated successfully, but these errors were encountered: