Bug#337073: tex-common doesn't install (can't chmod ls-R file)

[Frank Küster <frank@debian.org>]

Joe Drew <drew@debian.org> wrote:

> Package: tex-common
> Version: 0.9
> Severity: grave
>
> tex-common fails to install because it can't chmod an ls-R file.
> /var/lib/texmf exists on my system, but the ls-R file doesn't.
>
> Setting up tex-common (0.9) ...
> chmod: cannot access `/var/lib/texmf/ls-R': No such file or directory
[...]
> -- debconf information:
>   tex-common/groupname: cachegroup
>   tex-common/cnf_name:
>   tex-common/managedlsr: cache

This is strange: It tries to chmod on /var/lib/texmf/ls-R, but you have
chosen to manage only "cache", which corresponds to
/var/cache/fonts/ls-R.  I also cannot reproduce the bug:  When I install
tex-common and choose to manage "cache", and assign it to "cachegroup"
(which doesn't exist in my pbuilder environment, but that shouldn't make
a difference),  I get:

You can choose a specific group which the previously selected ls-R files should belong to. If you do not enter a group 
name here, the group ownership of the selected files will not be touched at all. If you have selected 'cache' in the 
previous question, we would suggest to select the group 'users' here.

Which group should own the ls-R files? cachegroup


chmod: cannot access `/var/cache/fonts/ls-R': No such file or directory
root@alhambra:/# 

So there is an error message (which is a bug), but it does not cause the
postinst to fail.

Joe, did you install from a system without any tex-common on it, or with
tex-common in rc state, or was it an upgrade (from which version)?

Norbert, do you have an idea?  It looks as if we should check for the
existence of the ls-R files before trying to chmod them, but that cannot
explain that it does not fail on my system (but gives an error message I
expected), but fails on Joe's with a message that is strange.

Regards, Frank

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