Control: tags -1 = upstream fixed-upstream
Control: fixed -1 vorta/0.11.2-1

Hi Mike,

mhaag85893 <[email protected]> writes:

> Hi, Nicholas
>
> Not being familiar with Borg, I'm convinced I messed something up on the 
> first install.

Truly, you didn't mess anything up! :) Rather, you found a bug that I
wasn't aware existed in Vorta 0.10.3.  The nature of the bug appears to
be that Vorta wasn't designed to accept an empty password.  Thank you
for reporting this bug and for following-up on the request for more
info.

> One thing I now realize I did, or rather didn't do, the first time 
> around was to set up the repository without providing a password. I 
> thought the password was only needed for SSH to a remote. So, instead of 
> using Vorta to set the repository, I ran this from the command line:
>
> $ borg init --encryption=repokey /mnt/IntrlBkUp/BkUp/BorgBkUp

Aha!  This was what was needed to reproduce.  I just confirmed that the
bug doesn't exist in 0.11.2, so now the question is if a sufficiently
small targeted fix can be made to 0.10.3-1 in trixie (13) that the
release team will unblock the bugfix (a bugfix can introduce regressions
in other areas, after all).

> That statement is derived from step 1, from Examples at $ info borg. The 
> info pages do mention passphrases, but they sound kind of optional.

You're right, they are optional...strictly speaking, because some people
want unencrypted backups, passwordless systems, autologin, etc.  It's a
bit tangential to this bug, but do you tend to prefer if (arguably
unsafe) user freedom or (arguably patronisingly paranoid) safe defaults
are prioritised?

> As I mentioned, deleting the borg cache: $ rm -r ~/.cache/borg/* got 
> things running in the first install.

I wonder why this worked?

>   Wanting to try a clean install, I purged Borg and Volta, deleted the 
> repository, deleted ~/.cache/borg and reinstalled. Once I supplied a 
> password, Volta immediately setup the repository. It's running great 
> now: A 4.3 GB backup in just over 2 minutes.

Great to hear :)

Best,
Nicholas

Attachment: signature.asc
Description: PGP signature

Reply via email to