Bug#662994: marked as done (installation fails, fmtutil-sys failed)
Your message dated Thu, 08 Mar 2012 22:42:50 +0200
with message-id <1331239370.1197.1.camel@vanquo.pezone.net>
and subject line Re: Bug#662994: installation fails, fmtutil-sys failed
has caused the Debian Bug report #662994,
regarding installation fails, fmtutil-sys failed
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.)
--
662994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662994
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-binaries
Version: 2009-12
Severity: important
I ran into this problem while trying to build the slony1-2 package in
a cowbuilder environment. During the installation of the build
dependencies, the installation of texlive-binaries fails. To be sure,
I have rebootstrapped the cowbuilder environment from scratch. Then I ran
cowbuilder --login
and to simulate the installation of the build dependencies
apt-get install --no-install-recommends autotools-dev bison debhelper docbook docbook-xml docbook2x docbook-dsssl docbook-utils flex ghostscript groff libjpeg-progs libpq-dev netpbm openjade opensp postgresql-server-dev-all
which fails later with
...
Setting up texlive-binaries (2009-12) ...
update-alternatives: using /usr/bin/xdvi-xaw to provide /usr/bin/xdvi.bin (xdvi.bin) in auto mode.
update-alternatives: using /usr/bin/bibtex.original to provide /usr/bin/bibtex (bibtex) in auto mode.
mktexlsr: Updating /var/lib/texmf/ls-R-TEXMFMAIN...
mktexlsr: Updating /var/lib/texmf/ls-R-TEXLIVE...
mktexlsr: Updating /var/lib/texmf/ls-R...
mktexlsr: Done.
Building format(s) --refresh.
This may take some time...
fmtutil-sys failed. Output has been stored in
/tmp/fmtutil.G7ameD1n
Please include this file if you report a bug.
dpkg: error processing texlive-binaries (--configure):
subprocess installed post-installation script returned error exit status 1
...
The contents of /tmp/fmtutil.G7ameD1n is:
"""
mkdir: cannot create directory `/tmp/user/1000/fmtutil.5306': No such file or directory
fmtutil: could not create directory `/tmp/user/1000/fmtutil.5306'.
"""
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (101, 'experimental')
Architecture: i386 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages texlive-binaries depends on:
ii ed 1.6-1
ii libc6 2.13-26
ii libfontconfig1 2.8.0-3.1
ii libfreetype6 2.4.8-1
ii libgcc1 1:4.6.3-1
ii libkpathsea5 2009-12
ii libncurses5 5.9-4
ii libpng12-0 1.2.47-1
ii libpoppler13 0.16.7-3
ii libstdc++6 4.6.3-1
ii libtinfo5 5.9-4
ii libx11-6 2:1.4.4-4
ii libxaw7 2:1.0.9-3
ii libxmu6 2:1.1.0-3
ii libxpm4 1:3.5.9-4
ii libxt6 1:1.1.1-2
ii perl 5.14.2-7
ii tex-common 2.10
ii texlive-common 2009-15
ii zlib1g 1:1.2.6.dfsg-2
Versions of packages texlive-binaries recommends:
ii texlive-base 2009-15
texlive-binaries suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On tor, 2012-03-08 at 07:57 +0900, Norbert Preining wrote:
> On Mi, 07 Mär 2012, Peter Eisentraut wrote:
> > mkdir: cannot create directory `/tmp/user/1000/fmtutil.5306': No such file or directory
> > fmtutil: could not create directory `/tmp/user/1000/fmtutil.5306'.
>
> Aehm, did you set up TMPDIR/TEMP/TMP in a strange way? The code is
> tmpdir=${TMPDIR-${TEMP-${TMP-/tmp}}}/$progname.$$
> so I can only suppose that something is not properly set up in your
> cowbuilder root, like not existing temp directory or that kind.
>
> Can you please verify that this is a clean and untempered pbuilder/cowbuilder
> environment?
It was due to libpam-tmpdir. Sorry for the noise.
--- End Message ---
Reply to: