TW
Interesting. I made a backup, maybe also restarted vorta and now I get this again: So the value selection is disabled, again. So guess that does not confirm my theory...
I can also reproduce this for vorta built from master branch: after starting vorta, the values are not enabled.
I think in `SchedulePage`, `populate_from_profile` needs to be called **after** the connections are set up.
Not sure if vorta already supports recent betas of borg2? There were quite big changes.
I filed a PR so vorta can run with borg2 >= 2.0.0b10.
I just restarted vorta, still the same: it wants to use the bundled borg. ``` 2024-10-18 21:05:20,068 - vorta.i18n - DEBUG - Loading translation succeeded for ['en-DE', 'en-Latn-DE', 'de-DE', 'de-Latn-DE',...
Just checked out vorta master branch and installed it to a venv: That one finds the homebrew borg: ``` 2024-10-18 21:48:17,192 - vorta.borg.borg_job - INFO - Running command /opt/homebrew/bin/borg --version...
``` @classmethod def prepare_bin(cls): """Find packaged borg binary. Prefer globally installed.""" borg_in_path = shutil.which('borg') if borg_in_path: return borg_in_path elif sys.platform == 'darwin': # macOS: Look in pyinstaller bundle from Foundation...
That might be, but something is broken there. My borg is in `/opt/homebrew/bin` and does not get found by `shutil.which`.
BTW, IIRC finding the homebrew borg from vorta has worked for me at some time in the past. I remember installing the Apple Silicon version of borg from homebrew, so...