Description of problem:
I'm preparing to package xmobar (Bug #460974). xmobar crashes if xft is not built without utf8 support (and using an xft from cabal causes confusion and mass hysteria for some reason; maybe xmonad/xmobar not liking linking different builds?).
I see that X11-xft was rebuilt for rawhide, any plans for F-13 and lower?
What happens if you remove ghc-utf8-string*?
I think this confusion came about by ghc-6.12.1
accidently shipping a copy of utf8-string.
But you are right we should really rebuild
all the packages that depend on it.
Then xmobar is not built against it and crashes with UTF-8 characters in window titles. This has been fixed in xmobar 0.11 (not sure where, xmobar or xft), but the packages should still be rebuilt.
Need more details: point being that ghc-6.12.1 already includes utf8-string-0.3.4.
So for current f13 probably better to drop the dependency for now.
(I agree packages need rebuilding but that takes some time,
so just suggesting "workarounds" for now.:)
(xmobar should build fine in rawhide/f14 anyway so you could
still go ahead with its review - I will try to work on this
soon if noone else gets to it first. I blame ghc for
shipping utf8-string in ghc-6.12.1! :)
I started this with rebuild of ghc-X11-xft
Next will be ghc-xmonad-contrib.
ghc-X11-xft-0.3-8.fc13,ghc-xmonad-contrib-0.9.1-4.fc13 has been submitted as an update for Fedora 13.
ghc-X11-xft-0.3-8.fc13, ghc-xmonad-contrib-0.9.1-4.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update ghc-X11-xft ghc-xmonad-contrib'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/ghc-X11-xft-0.3-8.fc13,ghc-xmonad-contrib-0.9.1-4.fc13
ghc-X11-xft-0.3-8.fc13, ghc-xmonad-contrib-0.9.1-4.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.