TW

BTW, I reproduced the issue (see top post) with vorta 0.9.1 installed via brew. It also wants to use the bundled borg and not the one from homebrew.

Just found out that the `borgbackup-fuse` from homebrew does not work correctly, it misses `packaging`. Guess that could be the reason why vorta falls back to the bundled borg. https://github.com/borgbackup/homebrew-tap/issues/36

Hmm, I just uninstalled borgbackup-fuse, brew installed borgbackup, upgraded and restarted vorta and still get this:

I really think we need a debug log line printing the PATH there. Something is not as expected there and that would be a first step confirming that.

@greigdp See https://github.com/borgbase/vorta/issues/2100#issuecomment-2423136650 - I could not debug the issue because in a source based install it worked as expected (and I could not build the binary).

@greigdp Can you use `os.environ["PATH"]`? Should show the current PATH as in the vorta process and not create another process for the "echo $PATH".

Can confirm: - when vorta is started by "Vorta.app" being a "login item", it get the wrong, bundled borg-dir/borg.exe (intel) - when I invoke `/Applications/Vorta.app/Contents/MacOS/vorta-darwin` from a terminal, it says...

This makes it use the homebrew borg for me: ``` tw@MacBook-Pro ~ % defaults write com.apple.dt.Xcode UseSanitizedBuildSystemEnvironment -bool NO ``` Source: https://stackoverflow.com/a/26586170 Update: only works until logout or reboot, seems...

Any macOS developer / admin reading? It can't be that hard to modify the PATH so such stuff just works, can it?

@goebbe Yeah, good idea, needs to be considered. Some additional points: - users (and borg UIs/wrappers, like borgmatic, pika backup and vorta) likely use both. so dropping the --exclude is...