Hi, Am Montag, den 17.06.2013, 02:06 +0100 schrieb Colin Watson: > I'm not sure that moving the documentation to /usr/lib/ghc-doc/ (where > the symlinks currently reside; ignoring the /usr/lib/ vs. /usr/share/ > question) and symlinking from /usr/share/doc/ would really be the right > way to fix this. People stripping /usr/share/doc/ probably don't want > documentation and are not all that bothered about a few dangling > symlinks.
yes, we should fix hoogle just like we fixed the ghc-doc trigger: Just do nothing if the files from /usr/share/doc are no there. > Noting the "invalid byte sequence" error visible in this log, there are > two other ways to make this minimally work such that the postinst > succeeds. Making the keyword database exist is enough. keyword.txt > contains a single character not in ASCII, namely a zero-width space > (U+200B) on line 260. We could remove or replace that character; I'm > not sure that's sensible. Or we could run update-hoogle in the C.UTF-8 > locale, which these days is in libc-bin and therefore guaranteed to > exist. I'd lean towards that second option. Anyone else? There is a third option: Have upstream state that keyword.txt ought to be always in UTF8-mode and use the appropriate, non-local-dependent file operations. Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer [email protected] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [email protected] | http://people.debian.org/~nomeata
signature.asc
Description: This is a digitally signed message part
