Re: jadetex: support TexLive
clone 375037 -1
retitle -1 loading existing base format breaks tetex or texlive packages
severity -1 serious
tags -1 patch
Andreas Pakulat <firstname.lastname@example.org> wrote:
> Package: jadetex
> Version: 3.13-6
> Followup-For: Bug #375037
> I'd like to add that it is not as easy as changing the dependecies. I
> did that here and the package prevents configuration of texlive-base-bin,
> due to some problems with the fmtutil-call.
Indeed, and this is a problem that can also occur with teTeX alone.
Imagine the following scenario:
- tetex-base, tetex-bin and jadetex are installed, the formats are
- tetex-base and -bin are updated in the same dpkg run. Updating either
tetex--base or -bin requires all formats to be rebuilt (because of
[possible] changes in the engine's, pool files, input files, etc.), so
both postinst scripts will trigger a rebuild. After unpacking and
before configuration, tetex-bin's configuration file
/etc/texmf/fmt.d/01tetex.cnf exists, but there is also a
/etc/texmf/fmt.d/01tetex.cnf.dpkg-new. tetex-base will be configured
before tetex-bin. Because of the dpkg-new file, update-fmtutil called
by tetex-base's postinst will ignore information in 01tetex.cnf, but
it will not ignore 40jadetex.cnf which has no dpkg-new file.
- tetex-base's postinst calls fmtutil --all, and - woosh - there's no
information about the latex format which jadetex wants to load. Thus
fmtutil and tetex-base's postinst will fail.
The solution is to not load the pregenerated latex.fmt, but instead load
latex.ltx in jadetex.ini, just as latex.ini does it, before doing the
proper jadetex stuff. Consequently, the format line in the fmtutil.cnf
snippet must be changed:
--- /etc/texmf/jadetex/jadetex.ini 2005-01-15 07:05:06.000000000 +0100
+++ myjadetex.ini.new 2006-08-22 17:18:45.000000000 +0200
@@ -1,3 +1,8 @@
--- /etc/texmf/fmt.d/40jadetex.cnf 2005-03-09 14:05:08.000000000 +0100
+++ 40jadetex.cnf.new 2006-08-23 17:16:57.000000000 +0200
@@ -2,6 +2,6 @@
# invoke with 'fmtutil --cnffile <file>'
# format engine pattern-file arguments
-jadetex etex language.dat &latex jadetex.ini
-pdfjadetex pdfetex language.dat &pdflatex pdfjadetex.ini
+jadetex etex language.dat -translate-file=cp227.tcx *jadetex.ini
+pdfjadetex pdfetex language.dat -translate-file=cp227.tcx *pdfjadetex.ini
I should remark that this is something that we, the TeX maintainers,
were not aware of, so there's also no fault on the side of the jadetex
maintainer. xmltex has the same problem.
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)