Re: Critical infrastructure update failing in TLU alone

Howdy,

There was a longer than usual wait time when attempting to download that update this morning. Once it was updated I didn’t have any problems. 

Good Luck,
Herb Schulz


> On Aug 17, 2026, at 6:37 PM, Bruno Voisin <[email protected]> wrote:
> 
> Trying to update TL with TeX Live Utility on the Mac, I get a notice that a critical infrastructure update must be applied first.
> 
> update-latest-tlmgr.sh is downloaded OK, but then
> 
>    2026-08-17 21:00:57 +0000 Notice -[TLMAuthorizedOperation setUnderlyingPID:][2792]    tlu_ipctask checking in: pid = 3212 (/var/folders/jk/khszwygs023gr2sdrkk02w100000gn/T/TLMInfraUpdateOperation.nY5lY6/update-tlmgr-latest.sh --nox11 -- --debug)
>    2026-08-17 21:00:57 +0000 Notice tlu_ipctask[3211]    tlu_ipctask: child HOME = '/var/root'
>    2026-08-17 21:00:57 +0000 Notice tlu_ipctask[3211]    tlu_ipctask: current HOME = '/var/empty'
>    2026-08-17 21:00:58 +0000 Notice tlu_ipctask[3211]    Verifying archive integrity... All good.
>    2026-08-17 21:00:58 +0000 Notice tlu_ipctask[3211]    Uncompressing TeX Live Manager Updater
>    2026-08-17 21:00:58 +0000 Warning tlu_ipctask[3211]    0%    47%    95%  100%   MD5 checksums are OK.     0%    47%    95%  100%  ./runme.sh: line 15: kpsewhich: command not found
>    2026-08-17 21:00:58 +0000 Warning tlu_ipctask[3211]    ./runme.sh: Cannot find TeX Live root using kpsewhich --var-value=SELFAUTOPARENT.
>    2026-08-17 21:00:58 +0000 Warning tlu_ipctask[3211]    ./runme.sh: (no tlpkg/texlive.tlpdb and/or tlpkg/tlpobj/.)
>    2026-08-17 21:00:58 +0000 Warning tlu_ipctask[3211]    ./runme.sh: Please set your PATH as needed, otherwise it's hopeless.
>    2026-08-17 21:00:58 +0000 Notice -[TLMAuthorizedOperation _runUntilChildExit][2792]    kqueue noted that pid 3212 exited (/var/folders/jk/khszwygs023gr2sdrkk02w100000gn/T/TLMInfraUpdateOperation.nY5lY6/update-tlmgr-latest.sh --nox11 -- --debug)
> 
> Seen on two macOS versions (macOS 27.0 Beta 5 and 6) using two different CTAN mirrors. I don't have an older macOS version at hand to test, for the rest of the week.
> 
> I don't understand. TLU makes sure /Library/TeX/TeXbin is in PATH at the beginning of its run, kpsewhich is there and "kpsewhich --var-value=SELFAUTOPARENT" gives /usr/local/texlive/2026 as it should.
> 
> The infrastructure update works running either of
> 
>    sudo tlmgr update --self
>    sudo sh update-tlmgr-latest.sh
> 
> So why is only TLU affected?
> 
> Comparing with an earlier infrastructure update on July 12, that was successful,
> 
>    2026-07-12 09:51:32 +0000 Notice -[TLMAuthorizedOperation setUnderlyingPID:][1538]    tlu_ipctask checking in: pid = 1747 (/var/folders/1r/dhdtft1s4qgfjwbcpkfhqf5c0000gn/T/TLMInfraUpdateOperation.wDgYlT/update-tlmgr-latest.sh --nox11 -- --debug)
>    2026-07-12 09:51:32 +0000 Notice tlu_ipctask[1746]    tlu_ipctask: child HOME = '/var/root'
>    2026-07-12 09:51:32 +0000 Notice tlu_ipctask[1746]    tlu_ipctask: current HOME = '/var/empty'
>    2026-07-12 09:51:33 +0000 Notice tlu_ipctask[1746]    Verifying archive integrity... All good.
>    2026-07-12 09:51:33 +0000 Notice tlu_ipctask[1746]    Uncompressing TeX Live Manager Updater
>    2026-07-12 09:51:33 +0000 Notice tlu_ipctask[1746]    ./runme.sh: updating in /usr/local/texlive/2026...
>    2026-07-12 09:51:33 +0000 Notice tlu_ipctask[1746]    ./runme.sh: tlmgr version says this is TeX Live 2026,
>    2026-07-12 09:51:33 +0000 Notice tlu_ipctask[1746]    ./runme.sh: and this updater script created: Sat Jul 11 23:53:37 CEST 2026.
>    2026-07-12 09:51:33 +0000 Warning tlu_ipctask[1746]    0%    47%    95%  100%   MD5 checksums are OK.     0%    47%    95%  100%  + test x = x--upgrade
>    2026-07-12 09:51:33 +0000 Warning tlu_ipctask[1746]    + echo './runme.sh: proceeding with tlmgr update.'
>    2026-07-12 09:51:33 +0000 Warning tlu_ipctask[1746]    + mv ./master/bin .
>    2026-07-12 09:51:33 +0000 Notice tlu_ipctask[1746]    ./runme.sh: proceeding with tlmgr update.
> 
> it seems the order of operations has changed: previously runme.sh was run before uncompression took place, now it's the other way round.
> 
> But tl-makeself-from-tlnet, that creates update-tlmgr-r*.sh, hasn't changed in almost 3 years, so how can that be?
> 
> Bruno
> 
> 
> 
>