Hi, Am Samstag, den 27.12.2014, 18:37 +0100 schrieb Sven Bartscher: > > What are the symptoms of this again? Does it affect jessie? Is this > > release critical? > > The symptoms are, that if you try to build some package that uses > hgettext functions in its Setup.hs, cabal yells at you that a lot of > arguments aren’t known. Why do packages use hgettext in their setup? Localized build error messages? What packages do that? > This happens because, cabal install passes arguments to Setup.hs and > if Setup.hs has another library version it is likely that the command > line interfaces don’t match and Setup.hs refuses the arguments. > > Running runghc Setup.hs <command> still works, but that lacks many > features cabal has. So there is no way to compile packages depending > on hgettext and having the comfort of cabal. > > All in all I would treat this as release critical. > > > If we need to make sure that hgettext ist build against the newer > > version, we should patch it’s .cabal file. > > Then we had to patch the .cabal files of all packages that provide > Setup.hs functions* every time we update cabal. What packages are that, besides hgettext? > So I don’t know if that is really the way to go. Do you know if it’s > possible to alter the dependencies of a package through the cabal > command line? Do you mean "--constraint"? > If so, we could mark the affected packages and teach the devscripts > to compile them with the right version. Note that descripts never call cabal. Cabal is purely a user tool... > If not, devscripts could patch the .cabal file just before compiling, > but that imposes the risk of breaking the compilation by some broken > regex. > > * Functions for use in Setup.hs Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: F0FBF51F JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata
Attachment:
signature.asc
Description: This is a digitally signed message part