Re: Bug#388399: FTBFS problems on alpha, mips[el]: Please help debugging
- To: Thiemo Seufer <email@example.com>
- Cc: firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, Alex Owen <firstname.lastname@example.org>, Cyril Bouthors <email@example.com>
- Subject: Re: Bug#388399: FTBFS problems on alpha, mips[el]: Please help debugging
- From: Frank Küster <firstname.lastname@example.org>
- Date: Sat, 30 Sep 2006 19:06:31 +0200
- Message-id: <[🔎] email@example.com>
- In-reply-to: <[🔎] 20060930160554.GB30302@networkno.de> (Thiemo Seufer's message of "Sat, 30 Sep 2006 17:05:54 +0100")
- References: <firstname.lastname@example.org> <handler.s.C.email@example.com> <firstname.lastname@example.org> <20060923102215.GC8904@thinkpad> <email@example.com> <[🔎] firstname.lastname@example.org> <[🔎] 20060929103700.GD21205@mauritius.dodds.net> <[🔎] email@example.com> <[🔎] 20060930055438.GG4726@mauritius.dodds.net> <[🔎] firstname.lastname@example.org> <[🔎] 20060930160554.GB30302@networkno.de>
[Summary for the buildd people: We still need your input]
Thiemo Seufer <email@example.com> wrote:
>> > sudo mkdir -p /tmp/texfonts/source/jknappen/ec
>> > sudo mkdir -p /tmp/texfonts/tfm/jknappen/ec
>> > make -C docs/psdoc
>> > So somewhere, there is a very, very wrong assumption that it's ok to use a
>> > fixed, user-invariant path under /tmp for writing out fonts.
>> I do not think that this is a bug, and anyway it's unrelated to the
>> FTBFS problem. Previously fonts were created below /var, but this was
>> regarded as a security risk because users would be able to completely
>> fill up /var. Now the font cache is in the users' directories, and only
>> as a fallback it is in /tmp/texfonts.
> So, if I understand that correctly, the bug was fixed by running mktexmf
> as non-root, and the change of the cache location is only a collateral.
No, or I do not understand what you mean. The bug we are sending this
to, #388399, is still open and RC, and nothing was fixed. I was just
describing the history of the font cache, in order to have an argument
why a user-invariant font cache directory might be acceptable. But
that's a different issue, not related to #388399, and I have already
sent a mail to firstname.lastname@example.org to separate this out.
The bug #388399 still persists, and so far it only manifests itself on
three buildds for alpha, mips and mipsel, and no one else has been able
to reproduce it. And I must say that it really sucks to exchange so
many e-mails on the topic without any input from the people who actually
>> If the admin chooses to create an empty /tmp/texfonts hierarchy without
>> write access for users that need the font cache, that's equivalent to
>> him creating an empty /var/cache/fonts/... without users having write
>> access, in the old setup. You're allowed to shoot yourself into the
> AFAIU any user on the system could create /tmp/texfonts and break
> mktexmf that way.
You are right, and while that's not a problem in most cases (hardly any
system except buildds and build chroots have users without writable home
directories that use TeX, and obviously up to now no system had two of
them), it is a bug.
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)