Bug#850915: ghc: Please switch to llvm 3.8 or, better, 3.9

On Mon, 19 Jun 2017 13:31:33 + (UTC) Gianfranco Costamagna <locutusofb...@debian.org> wrote: > Hello, > >Now that we shipped strech, I really would like to see llvm 3.7 removed. > >Can we go ahead now ? > > > as said, with ghc 8.0.1 and 8.0.2 this seems a litt

Accepted xmonad 0.13-7 (source) into unstable

pkg-haskell-maintainers@lists.alioth.debian.org> Changed-By: Gianfranco Costamagna <locutusofb...@debian.org> Description: libghc-xmonad-dev - Lightweight X11 window manager${haskell:ShortBlurb} libghc-xmonad-doc - Lightweight X11 window manager${haskell:ShortBlurb} libghc-xmonad-prof -

Bug#892004: Please adapt to gnome-settings-daemon 3.28 by March 15

hello, >I am unable to do something this week. Could someone else apply the >change and upload the package? in deferred/2 G. ___ Pkg-haskell-maintainers mailing list Pkg-haskell-maintainers@lists.alioth.debian.org

Re: How to print test log in case of failures?

Hello James, >That whole file looks like a major source of unaligned accesses, at aglance, >and likely needs some attention to support a potential lack of 64-bit >(and, in general, any) unaligned accesses. so, thanks for the really helpful answer! Do you think it is ok to override the

How to print test log in case of failures?

Hello, I'm trying to sort out an armhf alignment issue that happens with haskell-th-utilities in Ubuntu (but I'm pretty sure this isn't an Ubuntu-specific issue, reason for Ubuntu to fail is probably because stuff is run on top of an arm64 kernel). Test suite logged to:

Re: Bug#853285: closed by Clint Adams <cl...@debian.org> (Bug#853285: fixed in ghc 8.0.2-3)

Hello, >Here's an updated patch for 8.0.2-9. committed (I don't even know how to test it properly) on git, but obviously not uploaded. (I don't think it is worth an upload) Please forward the patches upstream whenever possible! thanks G. ___

Bug#867853: gcc: error: unrecognized command line option ‘-no-pie’

control: forcemerge 871740 867853 > Okay, I'll take this to mean that if I submit a working/useful patch, you'll > apply it. I'll get to work on that. consider that: gcc-5 is not part of any Debian stable release, and gcc-4.9 is has been part of jessie for a while, but jessie was released

Bug#871740: gcc: error: unrecognized command line option ‘-no-pie’

control: forcemerge -1 867853 control: unarchive 867853 control: reopen 867853 control: tags 867853 moreinfo > Okay, I'll take this to mean that if I submit a working/useful patch, you'll > apply it. I'll get to work on that. consider that: gcc-5 is not part of any Debian stable release, and

[no subject]

salutations http://szbttx.com/editproduct.php?pair=274cv7a3xdn Thanks so much Gianfranco ___ Pkg-haskell-maintainers mailing list Pkg-haskell-maintainers@lists.alioth.debian.org

Bug#867853: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#867853: gcc: error: unrecognized command line option ‘-no-pie’)

Hello, >I'm not sure I understand this response. > >When you say "gcc-specific", are you saying that the Debian Haskell package >supports compilers other than gcc? It appears to me that it specifically >requires gcc. I mean, that the flag has been added by gcc, and a lot of programs in

Bug#865711: haskell-yaml: FTBFS everywhere (except all)

Hello, >I don't know what we should do here. The behavior of the embedded >libyaml differs from our libyaml and I'm not sure why, but it appears >to be on purpose. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865675 because the embedded yaml is more up-to-date wrt the Debian one, and for

Bug#850915: ghc: Please switch to llvm 3.8 or, better, 3.9

Hello, >Now that we shipped strech, I really would like to see llvm 3.7 removed. >Can we go ahead now ? as said, with ghc 8.0.1 and 8.0.2 this seems a little impossible, but as Clint said on debian-haskell >> last thing: should we switch llvm? wrt #850915 >I think the GHC 8.2 release

Bug#855627: ghc-doc: ships dangling symlink /usr/share/doc/ghc-doc/html/users_guide/prof_scc -> prof_scc.png

control: tags -1 pending >during a test with piuparts I noticed your package ships a dangling >symlink: Hi, committed on git master, not sure if worth an upload (I guess not) https://anonscm.debian.org/cgit/pkg-haskell/DHG_packages.git/commit/?id=be033b6558f51ae50b60c051e70ce3397d92f029

Bug#853285: ghc: Patch to add support for cross-compilation of GHC

Hello: >* ghc does have a test suite, but the Debian package doesn't run it. ghc-testsuite is the source package "running" it. (please don't ask me the reasons for the split :) ) G. ___ Pkg-haskell-maintainers mailing list

Bug#850920: Cabal-debian bundled packages

Hello Kei, On Tue, 17 Jan 2017 19:42:57 + David Fox wrote: > Fortunately or unfortunately, I made extensive changes to this code in > November: > I did apply your patch and the head result didn't change >

Bug#850915: ghc: Please switch to llvm 3.8 or, better, 3.9

Hello >Probably need to backport this upstream commit: > >https://git.haskell.org/ghc.git/commitdiff/672314cbeb8ac386a58f17dc4650dbdf4c55d8b5 probably not only that one, but at least 3 commits Unfortunately when I expressed the idea (and the commits) over irc on #debian-haskell or whatever I

llvm-toolchain-3.8 needs fix on armel, or ghc will be removed there.

Hi, simple as it. We would like to have only llvm-toolchain-3.8 and llvm-toolchain-3.9 in Stretch. So, in case nobody has a patch/opinion on making llvm-3.8+ build/work on armel, I'm afraid no haskell packages will be available there for Stretch. Simple as this, keeping llvm-3.7 just for armel

Bug#712228: Hardening flag -pie breaks compilation with GHC

Hi, >With this change the package builds fine in unstable and experimental, >thank you. oops fixed :) G. ___ Pkg-haskell-maintainers mailing list Pkg-haskell-maintainers@lists.alioth.debian.org

Re: Finding sponsor

yes, Debian Haskell Group (in cc) might give you some hints :) G. Il Giovedì 2 Giugno 2016 14:47, Marwan Rabbâa ha scritto: but still have a question this app is in haskell and I built i with stack https://www.stackage.org I do not thing stack use internal