[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Some TODOs (gitit, aeson, alex)


Am Freitag, den 06.04.2012, 11:22 +0100 schrieb Iain Lane:
> On Fri, Apr 06, 2012 at 12:10:06PM +0200, Joachim Breitner wrote:
> > > 
> > > I don't get this at all
> > > 
> > >   - I can't reproduce this when building in an unstable chroot
> > >   - I /can/ when building in an Ubuntu precise chroot
> > >   - I again cannot when I log into the chroot, install the build-deps
> > >     and build with dpkg-buildpackage.
> > 
> > maybe it depends on how the build is invoked, e.g. dpkg-buildpackage vs.
> > debian/rules build?
> I don't think so, since the first two chroot builds listed above are
> done in the same way, using sbuild.
> I've attached the two logs, perhaps you can spot a pertinent difference.

one difference spotted: On precise, libghc-parsec2-dev is installed.
Unlikely to cause the problem, but still worth a check, especially as
the buildd also installed parsec2. The reason seems to be that json was
built with parsec2 in 0.5-1, and with parsec3 in 0.5-2.

I’ll retry building gitit on the buildds, now that json is using

[a bit too late]

https://buildd.debian.org/status/fetch.php?pkg=gitit&arch=i386&ver=0.9-1&stamp=1332951695 is build against the newer json, and also fails. Should have checked that before issuing the rebuild. Guess I was on the wrong track. No further idea right now.

I guess Cabal preprocesses the file before passing it to haddock, due to
LANGUAGE CPP. Might something go wrong there? Can we somehow get hold of
any intermediate files?


Joachim "nomeata" Breitner
Debian Developer
  nomeata@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nomeata@joachim-breitner.de | http://people.debian.org/~nomeata

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: