Open mouse07410 opened 2 months ago
Any progress, workaround, or feedback?
Hi, sorry for the late reply!
Two problems/differences between successful and unsuccessful invocations that I see is that the successful one (which I ran standalone, not via topgrade) did not specify the full path for the apps.
Topgrade does not specify the full path, it always searches commands in $PATH
.
What will happen if you simply do:
$ sudo tlmgr update --self --all
Does it also error out?
I saw that with the successful one, you were using sudo -EH
, why did you do this? I am aware that the sudo
on many Linux distros will modify $PATH
, but for macOS, this does not seem to be true from my test(I am on macOS 13, Sudo version 1.9.5p2).
Also, can you do:
$ which tlmgr
$ sudo zsh # replace zsh with your shell
$ which tlmgr
Erroneous Behavior
Expected Behavior
Steps to reproduce
A bit hard, as this system is now running Privileged Access Module (doesn't just allow
sudo
based on/etc/sudoers
file).Possible Cause (Optional)
Two problems/differences between successful and unsuccessful invocations that I see is that the successful one (which I ran standalone, not via
topgrade
) did not specify the full path for the apps.Can you make an option to not specify full path? I think I understand the implications.
Problem persists without calling from topgrade
Did you run topgrade through
Remote Execution
I don't even know what that means.
Configuration file (Optional)
Additional Details
Operation System/Version: MacOS Sonoma 14.5 with Xcode-15.4 and stable Rust-1.79.
Installation: via
cargo install topgrade
Topgrade version:
Topgrade 15.0.0
Verbose Output (
topgrade -v
)Too verbose to paste (unless you want to go through a 3704 lines in a post), so here it is: topgr.out.txt