[tex-live] Bad perms in 2016 texmf ?

Ken Moffat zarniwhoop at ntlworld.com
Sat Jun 25 01:34:11 CEST 2016

On Fri, Jun 24, 2016 at 10:37:02PM +0000, Karl Berry wrote:
>     I *hope* this is me again doing something wrong, but for the moment
>     I think texmf this year has bad perms.
> You're speaking of texlive-20160523-texmf.tar.xz, I presume.  From tar
> tvf, looks like you are right.  Sigh.  Will check the others and fix all
> when I have a chance.  --thanks, karl.

I've had a bad day with this (forcing *all* texmf files to 644 was a
bad idea because I had overlooked the scripts).  For the moment I'm
rebuilding again, using the following commands post-install :

find /opt/texlive/${TEXYEAR}/texmf-dist -type d -perm 2750 -exec \
chmod -v 755 {} \;
find /opt/texlive/${TEXYEAR}/texmf-dist -type f -perm 744 -exec \
chmod -v 644 {} \;
find /opt/texlive/${TEXYEAR}/texmf-dist -type f -perm 600 -o -perm \
640 -exec chmod -v 644 {} \;

The first catches a few directories such as doc/latex/acroterm where
context (mtxrun) initially blew up when I ran it as a user.  I guess
that only a root install (and perhaps a root untar) preserves the
sgid bit.

The second gets over 2000 files where the perms look dodgy but I doubt
they cause any real harm.

The last one is where I keep making mistakes / typos : it is for
files like
texmf-dist/source/fonts/lh/tex/wrk/*/* (all 600)

texmf-dist/source/latex/acroterm/* and
texmf-dist/source/latex/lh/* (mostly 640)

I think I will still be failing to address
texmf-dist/makeindex/gmdoc/gmglo.ist which got installed as 700
instead of 644.

Yes, you CAN fool most of the people some of the time.

More information about the tex-live mailing list