Re: Critical infrastructure update failing in TLU alone
Karl Berry <[email protected]>
| Newsgroups | gmane.comp.tex.live |
|---|---|
| Message-ID | <[email protected]> |
macOS 27.0 Beta 6
Maybe the new mac beta is refusing to execute any program it does not like?
Did you install previous updates on this same OS version?
Or maybe there is some kind of new problem Apple is inflicting on what
the shell script is doing.
I (or rather the scripts) prepared this update in the same way as all
previous ones, and the actual update was tiny (a few lines in TLPDB.pm).
Nothing substantive changed on the TL side, afaik.
There are various things you can do to take the update more step by step.
Run it with --help. In particular, you might try running it with
--target foodir --noexec and then you should have the contents of the
archive without the script being run. Then you should have the script in
foodir/runme.sh and can run with sh -vx or otherwise debug. I think.
I haven't done this in a while.
- update-tlmgr-latest.sh, used by TLU, does neither of the two (I
think), which makes debugging more difficult.
I'll think about it, thanks.
Adam chose to use u-t-l.sh because it seemed simpler and possibly more
reliable to always do "disaster recovery" than run the update --self.
That seemed fine to all of us; we just never thought about the lack
of version number/backups. -k