[debiandoc-sgml-pkgs] Bug#338376: debiandoc-sgml-doc: FTBFS: debiandoc-sgml.en.pdf could not be generated properly

[Frank Küster]

Roland Stigge <stigge at antcom.de> wrote:

> Package: debiandoc-sgml-doc
> Version: 1.1.17
> Severity: serious
>
> Hi,
>
> building the package debiandoc-sgml-doc in a clean sid build environment
> (with pbuilder) on i386 results in:
[...]
> debiandoc2latexpdf: ERROR: debiandoc-sgml.en.pdf could not be generated properly
> debiandoc2latexpdf: rerun with the -v option to found out why
> debiandoc2latexpdf: or check the log file debiandoc-sgml.en.log
> make[1]: *** [all] Error 1
> make[1]: Leaving directory `/tmp/buildd/debiandoc-sgml-doc-1.1.17'
> make: *** [build-stamp] Error 2
> =========================================================================
>
> However, debiandoc-sgml.en.pdf has been created and looks fine. The log file
> only contains warnings, as far as I can see.

There is one error, too:

,----
| ! Package textcomp Error: Symbol \textcurrency not provided by
| (textcomp)                font family ppl in TS1 encoding.
| (textcomp)                Default family used instead.
| 
| See the textcomp package documentation for explanation.
| Type  H <return>  for immediate help.
|  ...                                              
|                                                   
| l.1515 \&curren; => \textcurrency
|                                  {}
| Your command was ignored.
| Type  I <command> <return>  to replace it with another command,
| or  <return>  to continue without it.
`----

Because of the "Default family used instead", it seems the error is not
fatal, but since it is reported as a "package error" (not warning),
pdflatex seems to return a nonzero exit code.

This error is reproducible with a minimal document like this:

\documentclass{article}
\usepackage{mathpazo}
\usepackage{textcomp}

\begin{document}

100 \textcurrency{}.

\end{document}

So one could argue it is a bug in tetex-extra (which provides the ppl
font family, Palatino).  On the other hand, you cannot expect that the
Palatino fonts will get a textcurrency symbol before etch is released,
if at all.

Therefore I think you will have to find a workaround, and I guess this
has to be done in debiandoc-sgml, not the doc package:  AFAICS the error
occurs when showing what debiandoc-sgml can do wrt special characters,
in other words, every document that uses &curren will get the same
error. 

By the way, I have no idea why this pops up now.

Regards, Frank
-- 
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer