TW

I wouldn't limit pre-backup to "checking conditions". Often this is used to bring the data into a backup-worthy state (like dumping an active database, doing a snapshot, etc.) and this...

extracting to non-empty target directories might lead to a mixup of present files and restored files.

@Golddouble that pretty much sounds like overengineered, unexpected behaviour. The task of a restore is to restore files, not move existing files around on your filesystem. And as it is...

BTW, just as an update from my side / borgbackup development: I have a Macbook Air M1 now (2020 model) and currently use borg and vorta to back it up....

Hmm, just noticed that the vorta app (installed via brew cask) is an intel binary, so on M1 cpus it will require rosetta translation. Can this be solved easily, like...

@ioExpander yeah, it would be nice if vorta would run natively. but guess we would need some pyQT5 apple wheel or so? otoh, vorta is not very cpu demanding -...

Doing a direct install via `pip install vorta`does not work, but this works: ``` brew install pyQt5 python3 -m venv --system-site-packages env . env/bin/activate pip install vorta export BORG_OPENSSL_PREFIX=/opt/homebrew/opt/[email protected] pip...

``` ERROR: pyQt5 from https://files.pythonhosted.org/packages/7c/5b/e760ec4f868cb77cee45b4554bf15d3fe6972176e89c4e3faac941213694/PyQt5-5.14.0.tar.gz#sha256=0145a6b7de15756366decb736c349a0cb510d706c83fda5b8cd9e0557bc1da72 has a pyproject.toml file that does not comply with PEP 518: 'build-system.requires' contains an invalid requirement: 'sip >=5.0.1

But there is more broken: ``` Using cached PyQt5-5.15.3.tar.gz (3.3 MB) Installing build dependencies ... done Getting requirements to build wheel ... done Preparing wheel metadata ... error ERROR: Command...

Considering the activity here and that still build issues are present, I guess it makes sense to reopen this.