yfprojects

Shouldn't this be as easy as storing the old mask when overriding and restoring it after creating the DB file? ```python3 old_mask = os.umask(0o0077) # control permissions of DB file...

Can you fill in [this template](https://github.com/borgbase/vorta/blob/master/.github/ISSUE_TEMPLATE/bug_report.md?plain=1) @aapris and post it here?

Thanks for implementing this @marco44 and congrats to your first contribution! 🎉

It shouldn't be possible that the error given relates to a source being deleted since the method is called immediately after clicking the button and as far as I know...

The hook names could look like the ones from borgmatic. > Yeah, good idea to move it into scripts. Should those scripts live in the settings folder or a user-defined...

> What do you mean? Below the pre- and post-backup command entries vorta states that the following env vars are available: `$repo_url, $profile_name, $profile_slug, $returncode`. > I recommend avoiding env...

> While we can deal with smaller differences, Vorta will also make a breaking change to properly adjust. Probably as Vorta v1.x If we only need minor changes, I wouldn't...

> You have probably missed that Vorta will stop working with older borg repositories when switching to borg 2.0. I would oppose that since this does not match vorta's philosophy....

I guess this should have quite the high priority since borg v2 is already in beta. I created a branch `borg-v2-support` which smaller PR implementing one of the changes listed...

> Pushed the [first commit](https://github.com/borgbase/vorta/commit/b6595b02727a7f10dde723619bca3e94ebf613de) to the new v2-branch. This already covers creating and listing a repo. 🎉 > > For now I'm positive that we can cover the changes...