Bug#357983: tetex-bin: mktexmf can't write new .mf files
Frank Küster <frank@debian.org> wrote:
> Did you read /usr/share/doc/tex-common/README.Debian? If not, would it have
> helped you understand the problem?
No, I didn't read it (recently), and yes of course I wouldn't have
sent a bug report if I had read it. Or wouldn't I ?
Since this problem occured suddenly after an upgrade, I assumed it was yet
another debian-messing-around-under-my-feet and I started to hunt the bug as
usual. Kind of a conditionned reflex. It didn't occur to me that this new
"behavior" was intentional.
>> Note for the reader potentially suffering from this problem: adding you to
>> this group is not enough. It is not even enough to start a new shell. You
>> have to really login again (or maybe newgrp would suffice ?) for the change
>> to take effect. If somebody can explain this to me, I'm interested.
>
> That's how it's always been on UNIX systems.
Thanks, I know, but this is no answer to my question.
> teTeX folks, I fear we have to revert this change and make the system
> insecure by default. I suggest that we change it only for fresh
> installations and leave unstable users to chmod -R.
I'm not opposed to that change. However, I still consider it a bug to
suddenly break working installations without further notice. And no,
README.Debian is not enough. There should be at least a big blinking red light
somewhere (probably at package upgrade time) warning the users that something
has changed.
--
Didier Verna, didier@lrde.epita.fr, http://www.lrde.epita.fr/~didier
EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 44 08 01 85
94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 53 14 59 22 didier@xemacs.org
Reply to: