mactex-texlive-20250216.pkg fails

[Bruno Voisin]

Hi Karl,

> If you want to look into it further, I would suggest looking at
> tlmgr-commands.log from the pretest vs. a 2024 or 2023
> installation. [...]
> 
> No, there are not more formats. [...]

I can confirm this: same number of formats, same build time.

Having all 3 of TL 2023, 2024 and 2025 installed, I get for "time sudo fmtutil-sys --refresh --all":

2025
sudo fmtutil-sys --refresh --all  116.13s user 2.96s system 93% cpu 2:07.63 total

2024
sudo fmtutil-sys --refresh --all  119.08s user 3.32s system 90% cpu 2:15.93 total

2023
sudo fmtutil-sys --refresh --all  111.32s user 3.17s system 93% cpu 2:02.79 total

The respective tlmgr-commands.log give about the same times. And the number of formats are always like

fmtutil [INFO]: disabled formats: 3
fmtutil [INFO]: successfully rebuilt formats: 56
fmtutil [INFO]: total formats: 59

Sorry for the erroneous recollections!

What is odd is that all 3 of Richard Koch, Herb Schulz and me made this same observation independently, that the format rebuilds after updates are taking longer than before.

Possibly this is just because we are pretesting, so there are more updates and formats to be rebuilt, than during normal TeX Live operation.


> To figure out the build time for a given format, we irritatinly don't
> output the dates for each one, but you can use the full mtime on the
> .fmt files, e.g.,
> 
> $ ls -l --full-time /usr/local/texlive/2024/texmf-var/web2c/luahbtex/lualatex.fmt
> -rw-rw-r-- 1 karl root 12266767 2024-03-13 09:35:28.000000000 -0700 /u/local/texlive/2024/texmf-var/web2c/luahbtex/lualatex.fmt
> 
> and then do a subtraction of a given fmt's mtime and the one that was
> built previously. Or whatever. You get the idea.
> 
> (Similarly, install-tl.log lacks even the beginning/ending timestamped
> lines above, but you can figure out the total duration from the .fmt times.)
> 
> --full-time is a GNU ls option, so I guess you won't have that on the
> Mac, but there must be an equivalent, either an option or another
> command (e.g., stat) to read the inode.

The log in the first message of this thread shows the SIGKILL appeared after reading hilatex.ini, so the hilatex format was being built. In tlmgr-commands.log this comes after uplatex-dev, and stat gives

% stat -l -t '%FT%T' /usr/local/texlive/2025/texmf-var/web2c/euptex/uplatex-dev.fmt
-rw-r--r-- 1 root wheel 3337416 2025-02-23T00:09:57 /usr/local/texlive/2025/texmf-var/web2c/euptex/uplatex-dev.fmt

% stat -l -t '%FT%T' /usr/local/texlive/2025/texmf-var/web2c/hitex/hilatex.fmt 
-rw-r--r-- 1 root wheel 13407680 2025-02-23T00:10:07 /usr/local/texlive/2025/texmf-var/web2c/hitex/hilatex.fmt

So 10 seconds to build hilatex.fmt, there shouldn't be anything special about it.

Bruno