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

Re: Pandoc build status?


Am Mittwoch, den 28.03.2012, 21:32 +0200 schrieb Iustin Pop:
> > > - mips, s390: virtual memory exhausted: Cannot allocate memory
> > > - mipsel: E: Caught signal 'Terminated': terminating immediately
> > > - hurd-i386: hlibrary.setup: /usr/bin/ghc-pkg: interrupted
> > > 
> > > I'm not familiar with the mips/s390 ports (do they really have so few
> > > virtual memory?), but at least the i386/sparc builds look like they
> > > should be retried, right? If so, is anyone familiar with requesting a
> > > retry?
> > 
> > I scheduled a retry, but if virtual memory is the bound then it maybe
> > well be that we have to remove the packages on these arches; not even a
> > machine with more physical memory would help. At least s390 has only
> > half the virtual memory that i386 has and indeed this causes a few
> > packages to fail.
> I see. I didn't know that pandoc has such high build requirements.
> It failed again on s390, I would presume it'll fail on mips too.
> Since I need pandoc to go from markdown to man page, does this mean I
> would be better served with storing the built man page in the debian/
> directory and VCS, and installing it directly (instead of building it
> from markdown at build time)? One less build dependency, but one more
> manual step. Hmmm…

yes, I think it is reasonable. Preferably add a rule to debian/rules so
that "make -f debian/rules debian/blubb.man" will build the man page so
that it is documented how exactly to build the manpage.


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: