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

Bug#613013: marked as done (luatex: fails to upgrade in absence of fmtutil.cnf)



Your message dated Mon, 11 Jun 2012 08:45:40 +0900
with message-id <20120610234540.GJ26716@gamma.logic.tuwien.ac.at>
and subject line Re: Bug#613013: luatex: fails to upgrade in absence of fmtutil.cnf
has caused the Debian Bug report #613013,
regarding luatex: fails to upgrade in absence of fmtutil.cnf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
613013: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613013
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: luatex
Version: 0.60.2-1
Severity: serious
Justification: Policy 7.2

Setting up luatex (0.60.2-1) ...
Building format(s) --byengine luatex.
	This may take some time... 
fmtutil-sys failed. Output has been stored in
/tmp/fmtutil.GqN8HXC0
Please include this file if you report a bug.

That file contains:

/usr/bin/fmtutil: line 362: /usr/share/texmf/texconfig/tcfmgr: No such file or directory
fmtutil: config file `fmtutil.cnf' not found.

So it seems that luatex fails to configure in absence of that config
file. I *guess* that this config file is put in place by the postinst
/ configure step of some other texlive package, maybe
texlive-base. Then luatex should (directly or indirectly) depend on
texlive-base. Possibly the bug is in a package that luatex depends on,
or recommends, rather than in luatex itself.

The information hereunder is for the state _after_ I fixed the issue
manually, by first having all texlive-related packages installed and
configured correctly.

-- System Information:
Debian Release: 6.0
  APT prefers stable
  APT policy: (500, 'stable'), (200, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_LU.UTF-8, LC_CTYPE=fr_LU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages luatex depends on:
ii  libc6                  2.11.2-7          Embedded GNU C Library: Shared lib
ii  libpng12-0             1.2.27-2+lenny4   PNG library - runtime
ii  libpoppler5            0.12.4-1.2        PDF rendering library
ii  zlib1g                 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages luatex recommends:
ii  texlive-luatex                2009-11    TeX Live: LuaTeX packages

luatex suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
On So, 10 Jun 2012, Hilmar Preusse wrote:
> You closed the bug by putting th bug # into the changelog, i.e. you
> stated that you found the reason and solved the problem. This is
> simply not correct!

Ok, closing this bug now: it is old, no response from OP for one
year, not reproducible, old versions of luatex/tex-common/texlive,
so it is just one more waste of bug hanging around.

Best wishes

Norbert
------------------------------------------------------------------------
Norbert Preining            preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan                                 TeX Live & Debian Developer
DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
------------------------------------------------------------------------
The fronting for the eighty-yard long marble-topped bar
had been made by stitching together nearly twenty thousand
Antarean Mosaic Lizard skins, despite the fact that the
twenty thousand lizards concerned had needed them to keep
their insides in.
                 --- The Book decribing Milliways' politically incorrect
                 --- decor.
                 --- Douglas Adams, The Hitchhikers Guide to the Galaxy


--- End Message ---

Reply to: