Re: texlive support in therion
- To: debian-tex-maint@lists.debian.org
- Subject: Re: texlive support in therion
- From: Wookey <wookey@aleph1.co.uk>
- Date: Thu, 15 Feb 2007 20:47:50 +0000
- Message-id: <[🔎] 20070215204750.GW30274@xios>
- In-reply-to: <20070101230228.GL10478@xios>
- References: <87fybci7cs.fsf@ID-223132.user.uni-berlin.de> <20061219095908.GB1832@gamma.logic.tuwien.ac.at> <20061219112006.GH1832@gamma.logic.tuwien.ac.at> <20061223005950.GX9665@xios> <458DB476.1000607@group-s.sk> <20070101230228.GL10478@xios>
On 2007-01-01 23:02 +0000, Wookey wrote:
> On 2006-12-23 23:57 +0100, Stacho Mudrak wrote:
> >
> > Therion is using:
> > plain metapost
> > plain pdfetex (because of memory requirements)
> > and by default, it has CM and CS (latin2) font mappings
Therion has been working OK with texlive for me, and builds fine on my
machine. However, I just tried building it in pbuilder by way of a
proper check for potential FTBFS problems, and it fails due to not
being able to find pdftex.fmt
The end of the build log says:
make -C ./thbook
make[2]: Entering directory
/tmp/buildd/therion-0.5.0/build-tree/therion/thbook'
pdftex thbook.tex
This is pdfeTeX, Version 3.141592-1.30.5-2.2 (Web2C 7.5.5)
kpathsea: Running mktexfmt pdftex.fmt
mktexfmt: format pdftex' not available.
I can't find the format file pdftex.fmt'!
Currently the build-deps are:
Build-Depends: debhelper (>> 5.0.0), dbs, perl (>= 5.5),
docbook-to-man, texlive-base-bin | tetex-bin, tcl8.4 | tclsh,
libvtk5-dev, libwxgtk2.6-dev, libfreetype6-dev
Some experimentation determined that installing either texlive-pdfetex
or texlive-base instead of texlive-base-bin, fixed the problem. As
texlive-pdfetex is smaller I have gone with that for the build dep I
am just about to upload. So this email just by way of info and
completeness, unless anyone thinks that there is a reason to use
texlive-base instead?
Wookey
--
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679
work: http://www.aleph1.co.uk/ play: http://wookware.org/
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Reply to: