Closed JanEricNitschke closed 2 weeks ago
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 text
to <2.1.2
?
Done
Would you also be able to make a Hackage revision to pin text to <2.1.2?
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. Increasing the lower bound on fsnotify solved it for me, but I wonder if it can be fixed upstream with more revisions.
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.
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
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
.https://github.com/haskell/text/pull/608 https://github.com/haskell/text/issues/623