Hello Joachim, On 09:13 Wed 02 Jul , Joachim Breitner wrote: > Dear Apollon, > > Am Dienstag, den 01.07.2014, 17:44 +0300 schrieb Apollon Oikonomopoulos: > > There are almost certainly more options that I didn't consider. Could > > someone with better insight of GHC internals please share their views on > > this issue? > > I think this should be discussed with upstream at glasgow-haskell-users, > as the problem is not Debian specific (unless I’m mistaken).
No, it's not Debian-specific at any rate. Can someone from the team take the discussion there, or should I do it? > But in any case I don’t see this being fixed on the GHC side until 7.10 > (at the earliest, if people help with Erik’s effort and this makes it > into the compiler). Maybe we should consider your first option (linking > tls against OpenSSL), after a license analysis of the packages we > include in Debian. Would you see if that compiles and works for you? And > what about libcurl4-nss-dev? Linking haskell-curl against the OpenSSL variant of cURL works and SSL is stable again. Unfortunately, the NSS variant does not work, it fails to load the CA certificate from a cert + key PEM file, and I can assume this will not be the only issue. Note that in main only 6 packages are linked against the NSS variant of libcurl, as opposed to 63 using OpenSSL and 293 using GnuTLS. I would really like to see two variants for libghc-curl-dev (OpenSSL + GnuTLS), but libcurl's packaging makes this difficult; we would either have to use two identical source packages with different B-Ds, or "manually" alter the linker path and provide the libcurl.so symlinks during build (which is an ugly hack of course). Greetings, Apollon -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
