Bug#285198: Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
On Sun, Dec 11, 2005 at 03:07:25PM +0100, Frank K?ster wrote: tags 285198 patch thanks Osamu Aoki [EMAIL PROTECTED] wrote: After reviewing my package, IO realized cjk-latex has been removed from testing. Until some fix is done on postinst script, it will not enter testing due to #285198 (Manual edit of texmf.cnf not recommended). It seems we need to add some script to /etc/texmf/texmf.d insted of screwing around with /etc/texmf/texmf.conf file. This needs to be fixed frst before my debian-reference since it depends on it. Any idea how to fix this? It's even easier: Simply drop the code from postinst and depend on Yes, I just did in NMU. tex-common (= 0.13) | tetex-bin ( 3.0) This looks a little strange, but the explanation is that tetex-bin in sarge and currently in etch already had the setting that cjk-latex wants to introduce; when the configuration files where moved from tetex-bin to tex-common we first forgot it, This much I understand. and I've now readded it in the SVN repository of tex-common; the next release will again include it. OK. tex-common's release will not limit cjk-latex's testing migration, because in testing it has tetex-bin ( 3.0) to satisfy the dependency. But why limit to 3.0. Is this because tetes-bin is required? Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#285198: Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Osamu Aoki [EMAIL PROTECTED] wrote: tex-common (= 0.13) | tetex-bin ( 3.0) This looks a little strange, but the explanation is that tetex-bin in sarge and currently in etch already had the setting that cjk-latex wants to introduce; when the configuration files where moved from tetex-bin to tex-common we first forgot it, This much I understand. and I've now readded it in the SVN repository of tex-common; the next release will again include it. OK. tex-common's release will not limit cjk-latex's testing migration, because in testing it has tetex-bin ( 3.0) to satisfy the dependency. But why limit to 3.0. Is this because tetes-bin is required? Well, the setting T1FONTS=...hbf is provided by tetex-bin_2.0.2*, and by tex-common since 0.13. It is not provided if you install tetex-bin_3.0-* together with tex-common 0.12. Therefore, we must make sure that only tetex-bin versions that provide the setting will satisfy the dependency, and that's 3.0. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Bug#285198: Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
tags 285198 patch
thanks
Osamu Aoki [EMAIL PROTECTED] wrote:
After reviewing my package, IO realized cjk-latex has been removed from
testing. Until some fix is done on postinst script, it will not enter
testing due to #285198 (Manual edit of texmf.cnf not recommended).
It seems we need to add some script to /etc/texmf/texmf.d insted of
screwing around with /etc/texmf/texmf.conf file.
This needs to be fixed frst before my debian-reference since it depends
on it. Any idea how to fix this?
It's even easier: Simply drop the code from postinst and depend on
tex-common (= 0.13) | tetex-bin ( 3.0)
This looks a little strange, but the explanation is that tetex-bin in
sarge and currently in etch already had the setting that cjk-latex wants
to introduce; when the configuration files where moved from tetex-bin to
tex-common we first forgot it, and I've now readded it in the SVN
repository of tex-common; the next release will again include it. But
tex-common's release will not limit cjk-latex's testing migration,
because in testing it has tetex-bin ( 3.0) to satisfy the dependency.
Attached is a patch to achieve this.
Regards, Frank
diff -Nur cjk-latex-4.5.1.orig/debian/changelog cjk-latex-4.5.1/debian/changelog
--- cjk-latex-4.5.1.orig/debian/changelog 2005-12-11 14:50:58.459814408 +0100
+++ cjk-latex-4.5.1/debian/changelog 2005-12-11 14:44:22.003084992 +0100
@@ -1,3 +1,10 @@
+cjk-latex (4.5.1-4.1) unstable; urgency=low
+
+ * Do not mess around with the generated file texmf.cnf; instead depend
+on tex-common (= 0.13) which provides the font support we need.
+
+ -- Frank Küster [EMAIL PROTECTED] Sun, 11 Dec 2005 14:31:05 +0100
+
cjk-latex (4.5.1-4) unstable; urgency=low
* CVS update as of 2003-02-11.
diff -Nur cjk-latex-4.5.1.orig/debian/control cjk-latex-4.5.1/debian/control
--- cjk-latex-4.5.1.orig/debian/control 2005-12-11 14:50:58.462813952 +0100
+++ cjk-latex-4.5.1/debian/control 2005-12-11 14:43:23.812931240 +0100
@@ -7,7 +7,7 @@
Package: cjk-latex
Architecture: any
-Depends: ${shlibs:Depends}, tetex-base (= 1.0-1), tetex-bin (= 1.0.6-1.1)
+Depends: ${shlibs:Depends}, tetex-base (= 1.0-1), tetex-bin (= 1.0.6-1.1), tex-common (= 0.13)
Recommends: freetype1-tools
Suggests: tfm-arphic-bsmi00lp, tfm-arphic-bkai00mp, tfm-arphic-gbsn00lp, tfm-arphic-gkai00mp, hbf-jfs56, hbf-cns40-b5, hbf-kanji48
Description: A LaTeX macro package for CJK (Chinese/Japanese/Korean)
diff -Nur cjk-latex-4.5.1.orig/debian/postinst cjk-latex-4.5.1/debian/postinst
--- cjk-latex-4.5.1.orig/debian/postinst 2005-12-11 14:50:58.463813800 +0100
+++ cjk-latex-4.5.1/debian/postinst 2005-12-11 14:44:50.159804520 +0100
@@ -18,10 +18,3 @@
#DEBHELPER#
-# Fixes /etc/texmf/texmf.cnf.
-# Remove the following line when Debian's teTeX package comes with
-# the same setting.
-if ! /bin/grep -q '^T1FONTS.*;$TEXMF/fonts/hbf//' /etc/texmf/texmf.cnf; then
-/usr/bin/perl -pi -e 's|^(T1FONTS.*)$|$1;\$TEXMF/fonts/hbf//|;' \
- /etc/texmf/texmf.cnf
-fi
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Processed: Re: Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Processing commands for [EMAIL PROTECTED]: tags 285198 patch Bug#285198: Manual edit of texmf.cnf not recommended Tags were: fixed Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
After reviewing my package, IO realized cjk-latex has been removed from testing. Until some fix is done on postinst script, it will not enter testing due to #285198 (Manual edit of texmf.cnf not recommended). It seems we need to add some script to /etc/texmf/texmf.d insted of screwing around with /etc/texmf/texmf.conf file. This needs to be fixed frst before my debian-reference since it depends on it. Any idea how to fix this? Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341849: [debiandoc-sgml-pkgs] Bug#341849: Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
On Sat, Dec 03, 2005 at 10:19:57PM +0100, Jens Seidel wrote: Osamu, Ardo: time to upload ... Later, I have no time now. PS: I'm not sure about #337259. It is not necessary to remove broken version of debiandoc-sgml from debian-reference's build-depends, is it? Is a special action needed to ask the buildds to rebuild debian-reference? No. FTBFS is just bug type. This is all package thus does not get rebuild by buildd autobuilder. Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341849: Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Jens Seidel [EMAIL PROTECTED] wrote:
On Thu, Dec 01, 2005 at 07:30:17PM +0100, Frank Küster wrote:
I have looked into this bug, and it seems that it is the fault of
debiandoc-sgml. With reference.zh-cn.sgml, it produces the following
LaTeX code
\ifpdf
\usepackage[colorlinks=true,CJKbookmarks]{hyperref}
\else
\usepackage[hypertex]{hyperref}
\fi
If this is changed to
\ifpdf
\usepackage[colorlinks=true,CJKbookmarks]{hyperref}
\else
\usepackage[hypertex,CJKbookmarks]{hyperref}
\fi
the PS file can be produced without problems.
Not with tetex-bin 2.0.2-31, maybe with version 3.
This is a little surprising; however not too much, since CJKbookmarks
is an undocumented option, no wonder that it changed its behaviour.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Hi Osamu, On Sat, Dec 03, 2005 at 12:38:10PM +0900, Osamu Aoki wrote: On Fri, Dec 02, 2005 at 02:57:32PM +0100, Frank Küster wrote: Jens Seidel [EMAIL PROTECTED] wrote: If yes, you should use CJKbookmarks also for DVI files, as indicated above. If not (and I recommend that), simply do not load hyperref at all when producing dvi (unless you want to distribute DVI files, too). Hmmm... I am lost in LaTeX world. Current debiandoc-sgml has functionality to modify generated latex file using messy but simple shell script called fixlatex. The default symple one is in debiandoc-sgml but the most elaborate one is in debian-reference. Right. Please note that it was part of the package to work also in a old Woody environment. Since www-master was updated to Sarge we should remove ugly workarounds which where integrated into debiandoc-sgml. Nevertheless there were also a few package related fixes, such as Polish quotation style which is not FTBFS or debiandoc-sgml related. As I reviewed this cutomized bin/fixlatex in debian-reference, I was surprized how it grew so much. It looks like we can add this there. It would only be another hack. I reassigned the bug to debiandoc-sgml and prepare a new upload. But I first need a few hour to test it on all documents from DDP, in current testing and Sarge environment. Please upload when you see my commit to debiandoc-sgml CVS repository. As I have been updating debiandoc-sgml, I can fix some bugs from here too. (I have to be careful not to break previous work arounds.) That is to fix files in tools/lib/Format in the source tree of debiandoc-sgml and there is LaTeX.pm is good candidates. For this issue, I do not know which is better. Right, LaTeX.pm is the correct file to patch. My question is: Is this issue caused by other broken package? (it seems YES.) I assumed a problem in dvips with option -z. But since dvips just converts a dvi file to ps I understand that it requires a proper input file. Since -z option was introduced in 1.89 of debiandoc-sgml it was not well tested (I always try to test as much as possible, but it needs a very long time on my PIII 800 mini notebook). Should all debiandoc-sgml based package get this fix? If a document was supported by the current debiandoc-sgml package there is no need to rebuild it or to change the build dependencies ... Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#341849: Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
On Thu, Dec 01, 2005 at 07:30:17PM +0100, Frank Küster wrote:
I have looked into this bug, and it seems that it is the fault of
debiandoc-sgml. With reference.zh-cn.sgml, it produces the following
LaTeX code
\ifpdf
\usepackage[colorlinks=true,CJKbookmarks]{hyperref}
\else
\usepackage[hypertex]{hyperref}
\fi
If this is changed to
\ifpdf
\usepackage[colorlinks=true,CJKbookmarks]{hyperref}
\else
\usepackage[hypertex,CJKbookmarks]{hyperref}
\fi
the PS file can be produced without problems.
Not with tetex-bin 2.0.2-31, maybe with version 3. Avoiding dvips option
-z in case of trouble helps and doesn't use new, not yet verified code, so
I'm happy with this solution.
Osamu, Ardo: time to upload ...
PS: I'm not sure about #337259. It is not necessary to remove broken version
of debiandoc-sgml from debian-reference's build-depends, is it? Is a
special action needed to ask the buildds to rebuild debian-reference?
Jens
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Jens Seidel [EMAIL PROTECTED] wrote:
Here, again, we are at a point were the debiandoc-sgml maintainers need
to decide (perhaps you have, but I don't know yet):
Do you want to produce PDF files only with pdflatex, or is there a
reason to create them via latex/dvips/ps2pdf?
PDF files are not created using latex/dvips/ps2pdf! (See again #321942.)
So why not simply drop hyperref at all in this case?
If yes, you should use CJKbookmarks also for DVI files, as indicated
above. If not (and I recommend that), simply do not load hyperref at
all when producing dvi (unless you want to distribute DVI files, too).
Since our packages FTBFS all the time it may be a good idea to add an
option to debiandoc2latex to specify the further processing.
Why do you think you need this? Isn't
\ifpdf
\usepackage[colorlinks=true,CJKbookmarks]{hyperref}
\fi
enough? This will ignore hyperref completely for dvi generation, and
thus for ps generation.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
On Fri, Dec 02, 2005 at 02:57:32PM +0100, Frank Küster wrote:
Jens Seidel [EMAIL PROTECTED] wrote:
Here, again, we are at a point were the debiandoc-sgml maintainers need
to decide (perhaps you have, but I don't know yet):
Do you want to produce PDF files only with pdflatex, or is there a
reason to create them via latex/dvips/ps2pdf?
PDF files are not created using latex/dvips/ps2pdf! (See again #321942.)
So why not simply drop hyperref at all in this case?
If yes, you should use CJKbookmarks also for DVI files, as indicated
above. If not (and I recommend that), simply do not load hyperref at
all when producing dvi (unless you want to distribute DVI files, too).
Since our packages FTBFS all the time it may be a good idea to add an
option to debiandoc2latex to specify the further processing.
Why do you think you need this? Isn't
\ifpdf
\usepackage[colorlinks=true,CJKbookmarks]{hyperref}
\fi
enough? This will ignore hyperref completely for dvi generation, and
thus for ps generation.
Hmmm... I am lost in LaTeX world.
Current debiandoc-sgml has functionality to modify generated latex file
using messy but simple shell script called fixlatex. The default symple
one is in debiandoc-sgml but the most elaborate one is in
debian-reference.
As I reviewed this cutomized bin/fixlatex in debian-reference, I was
surprized how it grew so much.
It looks like we can add this there.
As I have been updating debiandoc-sgml, I can fix some bugs from here
too. (I have to be careful not to break previous work arounds.)
That is to fix files in tools/lib/Format in the source tree of
debiandoc-sgml and there is LaTeX.pm is good candidates. For this
issue, I do not know which is better.
My question is:
Is this issue caused by other broken package? (it seems YES.)
If this broken package is fixed, having workaround implimented cause
problem? or some missing featues? How serious?
Should all debiandoc-sgml based package get this fix?
Thanks for your help.
Osamu
PS: If either of you think having CVS access to debiandoc-sgml
(http://alioth.debian.org/projects/debiandoc-sgml/) or debian-reference
(project: qref.sourceforge.net), let me know your account there.
PS2: As I see some locale based issues such as usepackage{babel}...
this LaTeX.pm was better place to fix but I did not dare to do so back
then.
Osamu
Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Hi,
I have looked into this bug, and it seems that it is the fault of
debiandoc-sgml. With reference.zh-cn.sgml, it produces the following
LaTeX code
\ifpdf
\usepackage[colorlinks=true,CJKbookmarks]{hyperref}
\else
\usepackage[hypertex]{hyperref}
\fi
If this is changed to
\ifpdf
\usepackage[colorlinks=true,CJKbookmarks]{hyperref}
\else
\usepackage[hypertex,CJKbookmarks]{hyperref}
\fi
the PS file can be produced without problems.
Here, again, we are at a point were the debiandoc-sgml maintainers need
to decide (perhaps you have, but I don't know yet):
Do you want to produce PDF files only with pdflatex, or is there a
reason to create them via latex/dvips/ps2pdf?
If yes, you should use CJKbookmarks also for DVI files, as indicated
above. If not (and I recommend that), simply do not load hyperref at
all when producing dvi (unless you want to distribute DVI files, too).
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Hi,
thanks Frank for analysis and sorry to bother and waste your time so
often.
On Thu, Dec 01, 2005 at 07:30:17PM +0100, Frank Küster wrote:
I have looked into this bug, and it seems that it is the fault of
debiandoc-sgml. With reference.zh-cn.sgml, it produces the following
LaTeX code
\ifpdf
\usepackage[colorlinks=true,CJKbookmarks]{hyperref}
\else
\usepackage[hypertex]{hyperref}
\fi
If this is changed to
\ifpdf
\usepackage[colorlinks=true,CJKbookmarks]{hyperref}
\else
\usepackage[hypertex,CJKbookmarks]{hyperref}
\fi
the PS file can be produced without problems.
ah, interesting that only zh-cn fails, zh-tw and ja work.
Osamu: the new used dvips option -z (to support hyperlinks even after
latex/dvips/ps2pdf (which is not used by debiandoc-sgml but could be
used by others) was the reason for the break. I tried two weeks ago
debugging dvips without success.
Here, again, we are at a point were the debiandoc-sgml maintainers need
to decide (perhaps you have, but I don't know yet):
Do you want to produce PDF files only with pdflatex, or is there a
reason to create them via latex/dvips/ps2pdf?
PDF files are not created using latex/dvips/ps2pdf! (See again #321942.)
If yes, you should use CJKbookmarks also for DVI files, as indicated
above. If not (and I recommend that), simply do not load hyperref at
all when producing dvi (unless you want to distribute DVI files, too).
Since our packages FTBFS all the time it may be a good idea to add an
option to debiandoc2latex to specify the further processing. This is
slightly more complicated and would reduce output format features (no
links in dvi files (but dvi files are only used to run hyphen-show on
it?), no links after latex/dvips/ps2pdf cycle a user may start).
(Could a variable .tex file produce problems in Makefiles rules when it's
unsure whether the file belongs to pdflatex or latex/dvips?)
Osamu, it's your decision ...
Jens
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Somehow this mail was lost between gmail and my local machine. I found your mail from BTS web and writing you from my gmail web site. On 11/28/05, Frank Küster [EMAIL PROTECTED] wrote: Can you provide a source package for testing?I currently can't accessthe CVS, it seems. Sure. (CVS is at SF.NET. If you have account there, I can give you write access) Anyway, I will tar up source. (WARNING, this is big though.) and put it under people.debian.org/~osamu/pub/ . -- Osamu AOKI
Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Osamu Aoki [EMAIL PROTECTED] wrote: Hi, I am back with mail and internet connection. Although I merged Jens's patch which seems to be the same as what I did locally, I could not build under pbuilder. Sorry, which patch do you mean? I can't see it in the bug log, and I've worked on too many tetex-related bugs with patches in the last weeks to be able to remember where you were involved/Cc'ed. debiandoc2latexps -l $(echo zh-cn | bin/getlocale) reference.zh-cn.sgml debiandoc2latexps: ERROR: reference.zh-cn.ps could not be generated properly debiandoc2latexps: rerun with the -v option to found out why make[1]: *** [reference.zh-cn.ps] Error 1 make[1]: Leaving directory `/tmp/buildd/debian-reference-1.08' make: *** [build-stamp] Error 2 pbuilder: Failed autobuilding of package At least it is zh-cn only bug. Maybe, recent text file modifications of zh-cn are the cause of the problem. Did anyone succesful? Can you provide a source package for testing? I currently can't access the CVS, it seems. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Hi, I am back with mail and internet connection. Although I merged Jens's patch which seems to be the same as what I did locally, I could not build under pbuilder. ... debiandoc2latexps -l $(echo zh-cn | bin/getlocale) reference.zh-cn.sgml debiandoc2latexps: ERROR: reference.zh-cn.ps could not be generated properly debiandoc2latexps: rerun with the -v option to found out why make[1]: *** [reference.zh-cn.ps] Error 1 make[1]: Leaving directory `/tmp/buildd/debian-reference-1.08' make: *** [build-stamp] Error 2 pbuilder: Failed autobuilding of package At least it is zh-cn only bug. Maybe, recent text file modifications of zh-cn are the cause of the problem. Did anyone succesful? Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Jens Seidel [EMAIL PROTECTED] wrote: tetex-base (2.0.2a-2) unstable; urgency=low * By default, enable all hyphenation patterns in language.dat [frank] -- Frank Küster [EMAIL PROTECTED] Fri, 30 Jul 2004 12:55:50 +0200 Frank, I really don't understand why you think including all hyphenanation patterns by default should be requested from teTeX maintainers in the past. First of all languages.dat is a config file you knew about. Also I remember that LaTeX was always proud to need only very little resources such as RAM. And I also never assumed that one little project needing minor changes would influence a large package such as tetex. debian-reference was by no means the reason for this switch. Instead, the reasons were, IIRC: - many users found it hard to find the right place for this configuration, and furthermore didn't know they needed to recreate the formats afterwards - the code which we provided to make configuration of hyphenation patterns more user-friendly turned out to be error-prone - other TeX distributions also enable all available hyphenation patterns - it was reported that although the format generation takes longer, the effect during normal LaTeX runs is very small - and for the users that want to optimize even this, language.dat is still a conffile (in fact now this has changed again, and the conffile ist /etc/texmf/language.d/00tetex.cnf) And the most important reason was always that a config file can be changed by users so that it was the easiest way to ensure all requirements myself. During package build, it is not easy to do this, and also slow. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Daniel Schepler [EMAIL PROTECTED] wrote: Package: debian-reference Severity: serious Version: 1.08-4 From my pbuilder build log: ... ln -sf fix.txt.ent fix.ent debiandoc2text -l $(echo ja | bin/getlocale) quick-reference.ja.sgml bin/fixtxt ja quick-reference.ja.txt TEXINPUTS=3D$(pwd)/texmf/:$(kpsetool -n pdftex -p tex) \ pdftex -ini pdflatex.ini /dev/null make[1]: *** [pdflatex.fmt] Error 1 make[1]: Leaving directory `/tmp/buildd/debian-reference-1.08' make: *** [build-stamp] Error 2 I have looked into the makefile, and although I don't understand it completely, the approach to using LaTeX seems fundamentally flawed. Instead of building local formats, it would have been better to ask us teTeX maintainers to enable those languages. Now if it turns out that you still use languages that are not enabled or even existent in tetex in sid, the mechanisms for local formats described in the Debian TeX Policy Draft should be used - please look at the tex-common package. Second, it doesn't make sense to build the formats twice, once by calling an engine with -ini directly, and a second time using fmtutil. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Hi, first of all sorry for this late reply. On Sun, Nov 13, 2005 at 11:49:24AM +0100, Frank Küster wrote: Daniel Schepler [EMAIL PROTECTED] wrote: Package: debian-reference Severity: serious Version: 1.08-4 From my pbuilder build log: ... ln -sf fix.txt.ent fix.ent debiandoc2text -l $(echo ja | bin/getlocale) quick-reference.ja.sgml bin/fixtxt ja quick-reference.ja.txt TEXINPUTS=3D$(pwd)/texmf/:$(kpsetool -n pdftex -p tex) \ pdftex -ini pdflatex.ini /dev/null make[1]: *** [pdflatex.fmt] Error 1 make[1]: Leaving directory `/tmp/buildd/debian-reference-1.08' make: *** [build-stamp] Error 2 I have looked into the makefile, and although I don't understand it completely, the approach to using LaTeX seems fundamentally flawed. Instead of building local formats, it would have been better to ask us teTeX maintainers to enable those languages. Yes, you wrote this already in #265743. Since all languages are already supported in Sarge by default and www-waster (which creates DDP documents?) was upgraded to Sarge this week, I will remove the explicit format file creation. It was indeed not a nice solution but was useful in the past. tetex-base (2.0.2a-2) unstable; urgency=low * By default, enable all hyphenation patterns in language.dat [frank] -- Frank Küster [EMAIL PROTECTED] Fri, 30 Jul 2004 12:55:50 +0200 Frank, I really don't understand why you think including all hyphenanation patterns by default should be requested from teTeX maintainers in the past. First of all languages.dat is a config file you knew about. Also I remember that LaTeX was always proud to need only very little resources such as RAM. And I also never assumed that one little project needing minor changes would influence a large package such as tetex. And the most important reason was always that a config file can be changed by users so that it was the easiest way to ensure all requirements myself. Now if it turns out that you still use languages that are not enabled or even existent in tetex in sid, the mechanisms for local formats described in the Debian TeX Policy Draft should be used - please look at the tex-common package. I will look at this but most probably I will ignore it and remove the special language handling. It caused trouble in the past and the default should be OK. Second, it doesn't make sense to build the formats twice, once by calling an engine with -ini directly, and a second time using fmtutil. This should not happen. You are aware that # indicates a comment, right :-) TEXINPUTS=$$(pwd)/texmf/; \ pdfetex -ini pdftex.ini /dev/null # fmtutil --byfmt pdftex --fmtdir . Jens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create pdflatex.fmt
Package: debian-reference Severity: serious Version: 1.08-4 From my pbuilder build log: ... ln -sf fix.txt.ent fix.ent debiandoc2text -l $(echo ja | bin/getlocale) quick-reference.ja.sgml bin/fixtxt ja quick-reference.ja.txt TEXINPUTS=$(pwd)/texmf/:$(kpsetool -n pdftex -p tex) \ pdftex -ini pdflatex.ini /dev/null make[1]: *** [pdflatex.fmt] Error 1 make[1]: Leaving directory `/tmp/buildd/debian-reference-1.08' make: *** [build-stamp] Error 2 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-1-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
