Re: haskell-debian vs. newest HaXml

2009-09-09 Thread Antti-Juhani Kaijanaho
On Wed, Sep 09, 2009 at 08:31:11PM +0200, Joachim Breitner wrote: > Am Mittwoch, den 09.09.2009, 13:23 -0500 schrieb John Goerzen: > > I have no problem with offering the unstable HaXml in Debian, but only > > if the stable HaXml is still here! Agreed. > Anyways, it’s there now. How bad is the im

Re: [Pkg-haskell-maintainers] haskell-digest_0.0.0.6-1_amd64.changes REJECTED

2009-09-09 Thread Torsten Werner
Joachim Breitner schrieb: > I openend a bug, suggesting that. The bug got closed without a solution. Either zlib ships crc32.h or you regenerate crc32.h from source when building your package. Otherwise we can't be sure that the source of crc32.h gets lost in the future. Cheers, Torsten -- To

Re: haskell-debian vs. newest HaXml

2009-09-09 Thread John Goerzen
Jeremy Shaw wrote: > Hello, > > I can update Debian.Report to build against the newer HaXml now that > it is available in sid. And this is highly annoying. The stable HaXml (1.13) is now NOT available in sid. So that means that we can't build any software that uses the stable HaXml. I have n

Re: haskell-debian vs. newest HaXml

2009-09-09 Thread Joachim Breitner
Hi John, Am Mittwoch, den 09.09.2009, 13:23 -0500 schrieb John Goerzen: > Jeremy Shaw wrote: > > Hello, > > > > I can update Debian.Report to build against the newer HaXml now that > > it is available in sid. > > And this is highly annoying. The stable HaXml (1.13) is now NOT > available in s

Re: [Haskell-cafe] haskelldb and Debian

2009-09-09 Thread Joachim Breitner
Hi, Am Dienstag, den 08.09.2009, 22:30 +0200 schrieb Joachim Breitner: > As part of my haskell package catchup work, I updated haskelldb to > 0.12, > but I won’t come to package the odbc-* variants. So this task is up > for > takers for now :-) oh well, I just did it anyways :-) Packages in NEW.

Re: haskell-curl : FTBFS on alpha

2009-09-09 Thread Erik de Castro Lopo
Joachim Breitner wrote: > I suggest, unless you already have a clever idea how to fix this, to > just leave it like this. I'm sure the clever way to fix this is deep, involved and difficult :-). I'm also pretty sure there is no simple fix. I'll leave it :-). Erik -- ---

Bug#545810: RM: haskelldb-hsql, haskelldb-hsql-mysql, haskelldb-hsql-odbc, haskelldb-hsql-postgresql, haskelldb-hsql-sqlite3 -- ROM; Abodonned upstream

2009-09-09 Thread Joachim Breitner
Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, the source packages mentioned above ought to be removed from Debian. They do no longer compile and there is no upstream development happening. Their functionality is provided by the haskelldb-hdbc-* series

Re: haskell-curl : FTBFS on alpha

2009-09-09 Thread Joachim Breitner
Hi Am Mittwoch, den 09.09.2009, 19:21 +1000 schrieb Erik de Castro Lopo: > > Did you talk to any knowledgable upstream yet? > > My email to haskell-cafe has gone un-answered. > > I've also searched the upstream GHC bug tracker and found nothing. I suggest, unless you already have a clever idea

Re: haskell-curl : FTBFS on alpha

2009-09-09 Thread Erik de Castro Lopo
Joachim Breitner wrote: > That depends: If it is just a fact that non-32-bit stuff does not work > on alpha, The error message says: On Alpha, I can only handle 32 bytes of non-floating-point arguments to foreign export dynamic which to me suggests that on Alpha, calls to a foriegn func

Re: haskell-curl : FTBFS on alpha

2009-09-09 Thread Joachim Breitner
Hi, Am Mittwoch, den 09.09.2009, 08:04 +1000 schrieb Erik de Castro Lopo: > > Am Dienstag, den 08.09.2009, 09:54 +1000 schrieb Erik de Castro Lopo: > > > I've got this bug: > > > > > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540877 > > > > > > Any suggestions on how I might go about t

Re: haskell-debian vs. newest HaXml

2009-09-09 Thread Joachim Breitner
Hi Jeremy, Am Dienstag, den 08.09.2009, 19:33 -0500 schrieb Jeremy Shaw: > I can update Debian.Report to build against the newer HaXml now that > it is available in sid. Thanks. > The debian directory in Debain is what we use to build -- so it "works > for us". Do you use a modified hlibrar