Currently, xmonad does not build against the packages in the latest Stackage LTS release, in particular utf8-string-1. It would be great if xmonad would join stackage so that such problems are detected early. It also gives you some QA for free: http://www.stackage.org/authors
Comment #1
Posted on May 5, 2015 by Helpful HippoI just tried bumping the upper bound on the utf8-string dependency to ">= 0.3 && < 1.1" in xmonad.cabal and it appears to build fine against Stackage LTS 2.7. So I believe this is a one-line fix. A grep of the xmonad source reveals no use of the deprecated imports that were removed in the bump from 0.3.x to 1.0, and the same holds for XMonadContrib. I'll submit a patch.
Comment #2
Posted on May 9, 2015 by Helpful HorseAwesome, thanks!
Can you also send a pull request to add it to Stackage? http://www.stackage.org/authors
Comment #3
Posted on May 12, 2015 by Helpful HippoComment #4
Posted on May 12, 2015 by Helpful HippoThe pull request has been rejected because my patch to increase the bound on utf8-string hasn't made it to a released Hackage version yet. Is there a release planned yet? Does this merit a full point release on its own?
Comment #5
Posted on May 12, 2015 by Helpful RhinoWith my Debian packaging maintainer hat on: Yes, it does merit a release, either on its own or a proper new release.
Comment #6
Posted on May 31, 2015 by Helpful RhinoAny plans for a point release with this patch?
Comment #7
Posted on Jul 21, 2015 by Happy MonkeyBump. Still waiting on that release.
Status: Accepted