Debian Reference (zh_CN PS file) FTBFS

[Debian Bug Importer]

Automatically imported from Debian bug report #341849 http://bugs.debian.org/341849

[Frank Küster (frank-kuesterei)]

Daniel Schepler <email address hidden> 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

[Jens Seidel (jensseidel)]

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 address hidden> 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 address hidden> 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

[Frank Küster (frank-kuesterei)]

Jens Seidel <email address hidden> wrote:

> tetex-base (2.0.2a-2) unstable; urgency=low
>
> * By default, enable all hyphenation patterns in language.dat [frank]
>
> -- Frank Küster <email address hidden> 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

[osamu (osamu)]

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

[Frank Küster (frank-kuesterei)]

Osamu Aoki <email address hidden> 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

[Osamu Aoki (osamu-aoki)]

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 address hidden> wrote:
>
>
> Can you provide a source package for testing? I currently can't access
> the 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

[Frank Küster (frank-kuesterei)]

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

[Jens Seidel (jensseidel)]

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

[Frank Küster (frank-kuesterei)]

Jens Seidel <email address hidden> 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

[osamu (osamu)]

On Fri, Dec 02, 2005 at 02:57:32PM +0100, Frank Küster wrote:
> Jens Seidel <email address hidden> 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

[Jens Seidel (jensseidel)]

reassign 337259 debiandoc-sgml 1.1.89

[Jens Seidel (jensseidel)]

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 address hidden> 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

[Jens Seidel (jensseidel)]

reassign 337259 debian-reference
clone 337259 -1
reassign -1 debiandoc-sgml 1.1.89
retitle -1 Debian Reference (zh_CN PS file) FTBFS
thanks

Argh, there are two independent bugs which confused me.

First of all there original problem was
"debian-reference: FTBFS with new tetex-bin: Error trying to create
pdflatex.fmt" which is clearly a bug in debian-reference. We tried to
fix it and noticed that reference.zh_CN.ps could not be created. That's
a completly different bug, that's why I cloned the bug report.

Jens

[Debian Bug Importer (debzilla)]

Automatically imported from Debian bug report #341849 http://bugs.debian.org/341849

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Thu, 03 Nov 2005 16:23:53 +0100
From: Daniel Schepler <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: 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)

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 13 Nov 2005 11:49:24 +0100
From: =?iso-8859-1?q?Frank_K=FCster?= <email address hidden>
To: <email address hidden>
Subject: Re: debian-reference: FTBFS with new tetex-bin: Error trying to
 create pdflatex.fmt

Daniel Schepler <email address hidden> 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=3D3D$(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
--=20
Frank K=FCster
Inst. f. Biochemie der Univ. Z=FCrich
Debian Developer

[Debian Bug Importer (debzilla)]

Message-ID: <20051113151709.GA28554@pluto>
Date: Sun, 13 Nov 2005 16:17:09 +0100
From: Jens Seidel <email address hidden>
To: Frank =?iso-8859-1?Q?K=FCster?= <email address hidden>,
 <email address hidden>, <email address hidden>
Subject: Re: 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�wrote:
> Daniel Schepler <email address hidden> 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�<email address hidden> 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

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sun, 13 Nov 2005 19:37:30 +0100
From: =?iso-8859-1?q?Frank_K=FCster?= <email address hidden>
To: Jens Seidel <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: Bug#337259: debian-reference: FTBFS with new tetex-bin: Error
 trying to create pdflatex.fmt

Jens Seidel <email address hidden> wrote:

> tetex-base (2.0.2a-2) unstable; urgency=3Dlow
>
> * By default, enable all hyphenation patterns in language.dat [frank]
>
> -- Frank K=FCster <email address hidden> 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)=20

> 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
--=20
Frank K=FCster
Inst. f. Biochemie der Univ. Z=FCrich
Debian Developer

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 26 Nov 2005 20:56:35 +0900
From: Osamu Aoki <email address hidden>
To: Jens Seidel <email address hidden>, <email address hidden>
Cc: Frank =?iso-8859-1?Q?K=FCster?= <email address hidden>,
        <email address hidden>
Subject: Re: 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

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 28 Nov 2005 15:34:37 +0100
From: =?iso-8859-1?q?Frank_K=FCster?= <email address hidden>
To: Osamu Aoki <email address hidden>
Cc: Jens Seidel <email address hidden>, <email address hidden>,
 <email address hidden>
Subject: Re: Bug#337259: debian-reference: FTBFS with new tetex-bin: Error
 trying to create pdflatex.fmt

Osamu Aoki <email address hidden> 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 prope=
rly
> 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
--=20
Frank K=FCster
Inst. f. Biochemie der Univ. Z=FCrich
Debian Developer

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 30 Nov 2005 06:56:07 +0900
From: Osamu Aoki <email address hidden>
To: =?ISO-8859-1?Q?Frank_K=FCster?= <email address hidden>
Cc: Osamu Aoki <email address hidden>, Jens Seidel <email address hidden>,
 <email address hidden>, <email address hidden>
Subject: Re: Bug#337259: debian-reference: FTBFS with new tetex-bin: Error trying to create
 pdflatex.fmt

------=_Part_20670_15623412.1133301367456
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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=FCster <email address hidden> wrote:
>
>
> Can you provide a source package for testing? I currently can't access
> the 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

------=_Part_20670_15623412.1133301367456
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Somehow this mail was lost between gmail and my local machine.<br><br>
I found your mail from BTS web and writing you from my gmail web site.<br>
<br><div><span class=3D"gmail_quote">On 11/28/05, <b class=3D"gmail_sendern=
ame">Frank K=FCster</b> &lt;<a href=3D"mailto:<email address hidden>">frank@kue=
sterei.ch</a>&gt; wrote:</span><blockquote class=3D"gmail_quote" style=3D"b=
order-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; paddin=
g-left: 1ex;">
<br>Can you provide a source package for testing?&nbsp;&nbsp;I currently ca=
n't access<br>the CVS, it seems.<br></blockquote></div><br>
Sure.&nbsp; (CVS is at <a href=3D"http://SF.NET">SF.NET</a>.&nbsp; If you h=
ave account there, I can give you write access)<br>
<br>
Anyway, I will tar up source.&nbsp; (WARNING, this is big though.) and put =
it under <a href=3D"http://people.debian.org/~osamu/pub/">people.debian.org=
/~osamu/pub/</a> .<br>
<br>-- <br>Osamu AOKI<br>

------=_Part_20670_15623412.1133301367456--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Thu, 01 Dec 2005 19:30:17 +0100
From: =?iso-8859-1?q?Frank_K=FCster?= <email address hidden>
To: <email address hidden>
Cc: Osamu Aoki <email address hidden>,
 Jens Seidel <email address hidden>, <email address hidden>,
 <email address hidden>
Subject: Re: 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=3Dtrue,CJKbookmarks]{hyperref}
\else
\usepackage[hypertex]{hyperref}
\fi

If this is changed to=20

\ifpdf
\usepackage[colorlinks=3Dtrue,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).=20

Regards, Frank

--=20
Frank K=FCster
Inst. f. Biochemie der Univ. Z=FCrich
Debian Developer

[Debian Bug Importer (debzilla)]

Message-ID: <20051201194324.GA16330@pluto>
Date: Thu, 1 Dec 2005 20:43:24 +0100
From: Jens Seidel <email address hidden>
To: Frank =?iso-8859-1?Q?K=FCster?= <email address hidden>
Cc: <email address hidden>, Osamu Aoki <email address hidden>,
 Jens Seidel <email address hidden>,
 <email address hidden>, <email address hidden>
Subject: Re: 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�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

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 02 Dec 2005 14:57:32 +0100
From: =?iso-8859-1?q?Frank_K=FCster?= <email address hidden>
To: Jens Seidel <email address hidden>
Cc: <email address hidden>, Osamu Aoki <email address hidden>,
 Jens Seidel <email address hidden>, <email address hidden>,
 <email address hidden>
Subject: Re: Bug#337259: debian-reference: FTBFS with new tetex-bin: Error
 trying to create pdflatex.fmt

Jens Seidel <email address hidden> 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):
>>=20
>> 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).=20
>
> Since our packages FTBFS all the time it may be a good idea to add an
> option to debiandoc2latex to specify the further processing.=20

Why do you think you need this? Isn't

\ifpdf
\usepackage[colorlinks=3Dtrue,CJKbookmarks]{hyperref}
\fi

enough? This will ignore hyperref completely for dvi generation, and
thus for ps generation.

Regards, Frank
--=20
Frank K=FCster
Inst. f. Biochemie der Univ. Z=FCrich
Debian Developer

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 3 Dec 2005 12:38:10 +0900
From: Osamu Aoki <email address hidden>
To: Frank =?iso-8859-1?Q?K=FCster?= <email address hidden>
Cc: Jens Seidel <email address hidden>,
 <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: 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=FCster wrote:
> Jens Seidel <email address hidden> wrote:
>=20
> >> Here, again, we are at a point were the debiandoc-sgml maintainers need
> >> to decide (perhaps you have, but I don't know yet):
> >>=20
> >> 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.)
>=20
> So why not simply drop hyperref at all in this case?
>=20
> >> 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).=
=20
> >
> > Since our packages FTBFS all the time it may be a good idea to add an
> > option to debiandoc2latex to specify the further processing.=20
>=20
> Why do you think you need this? Isn't
>=20
> \ifpdf
> \usepackage[colorlinks=3Dtrue,CJKbookmarks]{hyperref}
> \fi
>=20
> 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. =20

Osamu

[Debian Bug Importer (debzilla)]

Message-ID: <20051203152658.GA14517@pluto>
Date: Sat, 3 Dec 2005 16:26:58 +0100
From: Jens Seidel <email address hidden>
To: <email address hidden>
Subject: Debian Reference's FTBFS is a debiandoc-sml bug

reassign 337259 debiandoc-sgml 1.1.89

[Debian Bug Importer (debzilla)]

Message-ID: <20051203154635.GA16361@pluto>
Date: Sat, 3 Dec 2005 16:46:35 +0100
From: Jens Seidel <email address hidden>
To: Osamu Aoki <email address hidden>, <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: 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�wrote:
> > Jens Seidel <email address hidden> 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

[Debian Bug Importer (debzilla)]

Message-ID: <20051203161345.GA17587@pluto>
Date: Sat, 3 Dec 2005 17:13:45 +0100
From: Jens Seidel <email address hidden>
To: <email address hidden>
Cc: Jens Seidel <email address hidden>, Osamu Aoki <email address hidden>
Subject: Splitting Debian Reference's bug report

reassign 337259 debian-reference
clone 337259 -1
reassign -1 debiandoc-sgml 1.1.89
retitle -1 Debian Reference (zh_CN PS file) FTBFS
thanks

Argh, there are two independent bugs which confused me.

First of all there original problem was
"debian-reference: FTBFS with new tetex-bin: Error trying to create
pdflatex.fmt" which is clearly a bug in debian-reference. We tried to
fix it and noticed that reference.zh_CN.ps could not be created. That's
a completly different bug, that's why I cloned the bug report.

Jens

[Jens Seidel (jensseidel)]

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

[Debian Bug Importer (debzilla)]

Message-ID: <20051203211957.GA13168@pluto>
Date: Sat, 3 Dec 2005 22:19:57 +0100
From: Jens Seidel <email address hidden>
To: Frank =?iso-8859-1?Q?K=FCster?= <email address hidden>
Cc: <email address hidden>, <email address hidden>,
 <email address hidden>
Subject: Re: 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�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

[Frank Küster (frank-kuesterei)]

Jens Seidel <email address hidden> 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

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Mon, 05 Dec 2005 08:28:02 +0100
From: =?iso-8859-1?q?Frank_K=FCster?= <email address hidden>
To: Jens Seidel <email address hidden>
Cc: <email address hidden>, <email address hidden>, <email address hidden>
Subject: Re: Bug#337259: debian-reference: FTBFS with new tetex-bin: Error
 trying to create pdflatex.fmt

Jens Seidel <email address hidden> wrote:

> On Thu, Dec 01, 2005 at 07:30:17PM +0100, Frank K=FCster 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
>>=20
>> \ifpdf
>> \usepackage[colorlinks=3Dtrue,CJKbookmarks]{hyperref}
>> \else
>> \usepackage[hypertex]{hyperref}
>> \fi
>>=20
>>=20
>> If this is changed to=20
>>=20
>> \ifpdf
>> \usepackage[colorlinks=3Dtrue,CJKbookmarks]{hyperref}
>> \else
>> \usepackage[hypertex,CJKbookmarks]{hyperref}
>> \fi
>>=20
>> the PS file can be produced without problems.
>
> Not with tetex-bin 2.0.2-31, maybe with version 3.=20

This is a little surprising; however not too much, since CJKbookmarks
is an "undocumented option", no wonder that it changed its behaviour.

Regards, Frank

--=20
Frank K=FCster
Inst. f. Biochemie der Univ. Z=FCrich
Debian Developer

[osamu (osamu)]

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

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 9 Dec 2005 00:31:54 +0900
From: Osamu Aoki <email address hidden>
To: Jens Seidel <email address hidden>, <email address hidden>
Cc: Frank =?iso-8859-1?Q?K=FCster?= <email address hidden>,
 <email address hidden>, <email address hidden>
Subject: Re: [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

[osamu (osamu)]

Source: debiandoc-sgml
Source-Version: 1.1.93

We believe that the bug you reported is fixed in the latest version of
debiandoc-sgml, which is due to be installed in the Debian FTP archive:

debiandoc-sgml_1.1.93.dsc
  to pool/main/d/debiandoc-sgml/debiandoc-sgml_1.1.93.dsc
debiandoc-sgml_1.1.93.tar.gz
  to pool/main/d/debiandoc-sgml/debiandoc-sgml_1.1.93.tar.gz
debiandoc-sgml_1.1.93_all.deb
  to pool/main/d/debiandoc-sgml/debiandoc-sgml_1.1.93_all.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Osamu Aoki <email address hidden> (supplier of updated debiandoc-sgml package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 03 Dec 2005 18:25:12 +0900
Source: debiandoc-sgml
Binary: debiandoc-sgml
Architecture: source all
Version: 1.1.93
Distribution: unstable
Urgency: medium
Maintainer: DebianDoc-SGML Pkgs <email address hidden>
Changed-By: Osamu Aoki <email address hidden>
Description:
 debiandoc-sgml - DebianDoc SGML DTD and formatting tools
Closes: 341849
Changes:
 debiandoc-sgml (1.1.93) unstable; urgency=medium
 .
   * Avoid using dvips option -z if it fails such as for Debian Reference's
     zh_CN dvi file (closes: Bug#341849). [jens]
Files:
 95f15c365a382f59333e998001f2d10d 666 text optional debiandoc-sgml_1.1.93.dsc
 d4d7719f95ee1a315980f27f8010dd20 99127 text optional debiandoc-sgml_1.1.93.tar.gz
 8e8bfcdc053012d260d31044733a512e 96612 text optional debiandoc-sgml_1.1.93_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDmv5X6A/EwagGHzIRAjUQAJ0fSnC3e3cR8TreuF8QZFjIR6xufgCggMNh
+5wIkemllMUNTnNTycQk83g=
=yYml
-----END PGP SIGNATURE-----

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Sat, 10 Dec 2005 08:02:06 -0800
From: Osamu Aoki <email address hidden>
To: <email address hidden>
Subject: Bug#341849: fixed in debiandoc-sgml 1.1.93

Source: debiandoc-sgml
Source-Version: 1.1.93

We believe that the bug you reported is fixed in the latest version of
debiandoc-sgml, which is due to be installed in the Debian FTP archive:

debiandoc-sgml_1.1.93.dsc
  to pool/main/d/debiandoc-sgml/debiandoc-sgml_1.1.93.dsc
debiandoc-sgml_1.1.93.tar.gz
  to pool/main/d/debiandoc-sgml/debiandoc-sgml_1.1.93.tar.gz
debiandoc-sgml_1.1.93_all.deb
  to pool/main/d/debiandoc-sgml/debiandoc-sgml_1.1.93_all.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Osamu Aoki <email address hidden> (supplier of updated debiandoc-sgml package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Mon, 03 Dec 2005 18:25:12 +0900
Source: debiandoc-sgml
Binary: debiandoc-sgml
Architecture: source all
Version: 1.1.93
Distribution: unstable
Urgency: medium
Maintainer: DebianDoc-SGML Pkgs <email address hidden>
Changed-By: Osamu Aoki <email address hidden>
Description:
 debiandoc-sgml - DebianDoc SGML DTD and formatting tools
Closes: 341849
Changes:
 debiandoc-sgml (1.1.93) unstable; urgency=medium
 .
   * Avoid using dvips option -z if it fails such as for Debian Reference's
     zh_CN dvi file (closes: Bug#341849). [jens]
Files:
 95f15c365a382f59333e998001f2d10d 666 text optional debiandoc-sgml_1.1.93.dsc
 d4d7719f95ee1a315980f27f8010dd20 99127 text optional debiandoc-sgml_1.1.93.tar.gz
 8e8bfcdc053012d260d31044733a512e 96612 text optional debiandoc-sgml_1.1.93_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDmv5X6A/EwagGHzIRAjUQAJ0fSnC3e3cR8TreuF8QZFjIR6xufgCggMNh
+5wIkemllMUNTnNTycQk83g=
=yYml
-----END PGP SIGNATURE-----

[Matt Zimmerman (mdz)]

Fixed in 1.1.93 and later:

debiandoc-sgml | 1.1.94 | http://us.archive.ubuntu.com dapper/main Packages