Re: Which version of ghc will stretch have?

2016-10-23 Thread Clint Adams
On Sun, Oct 23, 2016 at 04:24:12PM +, Clint Adams wrote: > Should we be doing -fno-PIE -fPIC instead? Or dropping -fno-PIE entirely?

Bug#841857: RFS: keysafe/0.20161022-1 [ITP]

2016-10-23 Thread Sean Whitton
Package: sponsorship-requests Severity: wishlist Control: block 834869 by -1 Dear mentors, I am looking for a sponsor for my package "keysafe". I would like this package to be uploaded **to experimental**. The reason for uploading to experimental is that Keysafe has not yet undergone a full

Re: Which version of ghc will stretch have?

2016-10-23 Thread Simon Michael
Thanks for working on this. I am close to releasing hledger[-*] 0.28, which should help with a lot of dependency issues. If necessary, I can do it today ?

Re: Which version of ghc will stretch have?

2016-10-23 Thread Clint Adams
On Sun, Oct 23, 2016 at 03:00:04PM +, Clint Adams wrote: > That doesn't seem to have worked. Should we be doing -fno-PIE -fPIC instead?

Re: Which version of ghc will stretch have?

2016-10-23 Thread Clint Adams
On Sun, Oct 23, 2016 at 01:44:03AM +0200, Iustin Pop wrote: > Ah, interesting, I didn't realise one could dig like that through the > dep chain. Looking at hledger-web -> libghc-yesod-static-dev -> > libghc-css-text-dev, which seems to fail with a quickcheck unittest > failure. Already reported

Re: Which version of ghc will stretch have?

2016-10-23 Thread Clint Adams
On Sat, Oct 22, 2016 at 09:19:21PM +, Clint Adams wrote: > I think in the long run, we'll want all our objects build with -fPIC, so > adapting the OpenBSD patch seems like the right approach. That doesn't seem to have worked.