-
Notifications
You must be signed in to change notification settings - Fork 802
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
vector-0.12.0.0 #2194
Comments
|
|
(Having said that, personally as maintianer I find the update comments really useful, but of course many people will get notified via github.) I suspect people can't update the checkboxes in my original comment? |
@juhp No, at least I can't. AFAIK only collaborators can edit/update comments. Now that I have a comment: Update: |
@juhp Correct. Not sure if it's possible to allow others to update the description of the issue without making them members of the project sadly. I believe I've made the necessary changes in Also, it appears |
@mdibaiee I've updated JuicyPixels' bounds on hackage (no need to make a new release), it compiles with Vector 0.12 |
|
Since we comment anyway: |
Thank you for all the Hackage updates: I have refreshed the initial comment. |
|
@paulrzcz AFAIK neither Generally, I hope that people actually test that their package is compiled against EDIT: the dependency graph of the libraries might be helpful in such big issues, there is no much one can do as a package maintainer of some leaf package (which happens to have direct dependency as well). |
@phadej After raising the vector version to 0.12.0.0 in extra-deps of stack.yaml and rebuilding the project with
Bumping of
The next step is to add interger-logarithms-1. So now hquantlib is buildable and has got extra-deps:
Studying the full dependency graph shows that Though, it builds without additional version bumps against Stackage nightly-2017-01-10 that already includes those versions of packages, except vector-0.12.0.0. |
@paulrzcz few things: use solver, e.g.
It's not visible in the output, but for Another thing, I noticed in
But |
|
|
New entry:
|
|
These mentions were originally truncated: @NicolasT @codedmart @tmcgilchrist @acid-state @jtobin @polarina @isomorphism @klao @nilcons @bgmari @mstksg @expipiplusx @fhaust @mgajda |
@bgamari * |
|
|
|
Whilst my package compiles nicely with vector-0.12.0.0, a change of behaviour in the vector package causes breakage. I hope this can be resolved within |
|
|
|
LTS 8 will be released soon, probably with After the LTS 8.0 release, the packages listed below (and any that depend on them) will continue to be included in LTS 8 builds, but will be dropped from nightly builds until a release compatible with
|
@DanBurton we've got a release coming soon that already fixes the vector bump and can easily fix the hspec bump, we're just doing some house cleaning before-hand because it's a big change for unrelated-to-Stackage reasons. |
Chart-1.8.2 uploaded. |
I’m updating |
|
|
I just pinged @gregorycollins again and he made a new release of (Also, I updated |
Thanks a lot, @byorgey, for the update! Very helpful |
vector-0.12.0.0 is out of bounds for:
Due to the large number of packages initially affected, there is no need to post update comments at this stage.
The text was updated successfully, but these errors were encountered: