-
Notifications
You must be signed in to change notification settings - Fork 139
vector-0.11.0.0 is (probably) breaking everything! #92
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
Comments
I bet this isn't the solver's fault but rather due to invalid meta-data on Hackage PS: I've read through #2759 (and commented there) and it seems the problem has been in fact identified as being caused by incorrect meta-data on Hackage which was fixed? Or does the problem still persist? |
2 hours ago I made a simple documentation change to https://github.com/fpco/inline-c (fpco/inline-c#32), and travic-ci failed with the same thing happening (https://travis-ci.org/fpco/inline-c/jobs/75569723):
So... Unless there is some caching happening, then this is not fixed upstream... |
The problem is quite clearly in
|
What I'm trying to get at with this issue report is: why does constraining the |
Why is the latest |
Because |
|
Ah, I see that the upper-bound constraint is in Thanks. |
I'm not entirely sure what the problem is, but it seems like the new
vector
package is incompatible with a few, also recent, packages, andcabal
's solver is deciding to install ancient versions of the latter packages rather than the slightly oldervector-0.10.12.3
, breaking stuff.Please see the following:
Is the issue with
vector
? How can it be rectified?I do not have the knowledge to analyse this further, but it obvious that something is not kashrut.
The text was updated successfully, but these errors were encountered: