-
Notifications
You must be signed in to change notification settings - Fork 42
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
Ambiguous occurrence ‘show’. #116
Comments
Thanks, fixed. I was just working towards a new release so hopefully that'll be out soon. |
Would you also be able to make a Hackage revision to pin |
Done |
Note this can cause build plans to pick fsnotify 0.4.0.1 because that one allows text 2.1.2 and then the build fails. |
Yeah, my CI ist still failing because it picks the old version that has neither the restriction nor fix as a transient dependency. Best would probably to publish a new proper release that includes the actual fix. |
Problem is this alone doesn't seem to fix the problem as cabal solver might pick a newer text over a newer fsnotify. The issue is that older versions also don't work with newer text so those need a revision. |
But the version on main (which would be the newest fsnotify) is compatible with the newest text version. |
Ah true. I was thinking main could have more restricted bounds than 0.4.0.1 on libraries other than text but that doesn't seem to be the case |
This is very much an issue. If you're going to not have upper bounds on dependencies, then it's necessary to bulk-revise older versions when something like this happens. This can be partially automated with https://hackage.haskell.org/package/hackage-cli. |
Okay, I revised all versions with the upper bound. |
I was just trying to build a package that depends on hsfnotify and found that it fails with the following error:
This seems to be due tot he addition of
show
in version 2.1.2 oftext
.haskell/text#608
haskell/text#623
The text was updated successfully, but these errors were encountered: