Hi, Am Freitag, den 03.07.2015, 16:29 -0400 schrieb Gwern Branwen: > On Fri, Jul 3, 2015 at 2:35 PM, Joachim Breitner <nomeata@debian.org> > wrote: > > For Debian’s purposes, that is not an ideal situation, and we will > > probably chose to remove it soon. It can be re-added later, if > > there is user demand, of course. > > It builds and runs fine with my current Debian testing system... > Other people on Github say it does not build and run fine on more > recent GHCs, and that is not something I can fix on my own since I am > not going to upgrade my own system to Debian unstable and risk my > other stuff just to see how mueval will run. but that’s a deadlock then: The Debian maintainers wait for you to upgrade your package in order to get new versions of GHC and libraries into testing while you wait for Debian to ship newer GHC and libraries... Clearly something is broken here :-) You can install a more recent version of GHC independently of the Debian packages and use that to make sure your packages work with reasonable new dependencies. I suggest to at least aim for compatibility with stackage LTS – this way, you are shielded from unrelated build failures in your dependencies. 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