Re: Critical infrastructure update failing in TLU alone
"Adam R. Maxwell" <[email protected]>
| Newsgroups | gmane.comp.tex.live |
|---|---|
| Message-ID | <[email protected]> |
> On Aug 21, 2026, at 11:38 , Bruno Voisin <[email protected]> wrote: > > Terminal has full disk access on my setup. I tried giving full disk access (in System Settings > Privacy & Security) to > > /Applications/TeX/TeX Live Utility.app TLU is not sandboxed, so it already has full disk access, I think. You're more likely to break things permanently by messing around like this, IMHO. > But maybe this isn't related at all. I imagine in a month or so when macOS OS 27 is released we'll see how things are. Has Apple responded to the bug report I assume you filed? That's the point of installing their OS betas, after all! I finally figured out why the LogEnvironment default wasn't working, though. Give this a try, and you should see what PATH is for the privileged task when you try updating: sudo -H defaults write com.googlecode.mactlmgr.tlmgr_cwrapper LogEnvironment -bool TRUE On Mojave, I have the PATH I expect: 2026-08-21 20:54:20 +0000 Notice tlu_ipctask[43310] tlu_ipctask: Current environment [...] PATH=/Library/TeX/texbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/texbin PWD=/Users/amaxwell/BuildProducts/Debug [...] Output from this and Karl's changes should be illuminating (and if Karl's are in tlcritical, you can try both). Adam