[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#267413: tetex-bin: Impossible to process a .tex



clone 267413 -1
retitle -1 tetex-bin should cater for changed debconf defaults
severity -1 important
retitle 267413 strange debiandoc2ps failure 
stop

Frank Küster <frank@debian.org> wrote:

> The problem is that I am quite sure this will *not* fix the problem for
> zope, because on the buildd's tetex-bin is always purged, anyway. I am
> currently investigating this in an sbuild environment on i386.

No problems to build with sbuild on i386. Furthermore, it is clear that
the problem with changed debconf defaults has nothing to do with the
FTBFS of zope - therefore I clone the bug, the zope issue is still grave.

This is why I know: When installing tetex-bin_2.0.2-19 with the "wrong"
settings discussed previously, i.e. with tetex-bin/fmtutil: false,
tetex-bin/upd_map: false, the output is as follows:

[...]
Creating config file /etc/texmf/texmf.d/95NonPath.cnf with new version
Generating /etc/texmf/texmf.cnf ... 
Creating config file /etc/texmf/texmf.cnf with new version
done
Running initex. This may take some time. ...
[...]

on the buildd's, e.g. on caballero (ia64),

http://buildd.debian.org/fetch.php?&pkg=zope&ver=2.6.4-1.2&arch=ia64&stamp=1093177931&file=log&as=raw

it looks different, indicating that the debconf questions are at their
new default, and fmtutil.cnf and updmap.cfg are created files:

[...]
Creating config file /etc/texmf/texmf.d/95NonPath.cnf with new version
Generating /etc/texmf/texmf.cnf ... 
Creating config file /etc/texmf/texmf.cnf with new version
done
Generating /var/lib/texmf/web2c/fmtutil.cnf ... done
Regenerating /var/lib/texmf/web2c/updmap.cfg ... done
Running initex. This may take some time. ...
[...]

> Pierre, which version of tetex-bin did you use for your build of
> zope_2.6.4-1.2_i386.deb? This is important, because the problems seem to
> be in fact architecture-independent.

This does no longer seem important, because I could build it with
2.0.2-19.

I really don't see any possibility to debug this, except somehow causing
the failing buildd's to build the package with "-v". 

Regards, Frank
-- 
Frank Küster, Biozentrum der Univ. Basel
Abt. Biophysikalische Chemie




Reply to: