Control: forwarded -1 https://github.com/borgbase/vorta/issues/916 Control: severity -1 important
Hi Sandro! Sorry for my delay replying, and thank you *very much* for reporting this bug. Sandro Tosi <mo...@debian.org> writes: > Package: vorta > Version: 0.7.5-1 > Severity: normal > > Hello, > i have a few unaccessible files, so vorta during the backup records that, and > the backup itself finished with a return code of 1. > > but the notification says "backup successful" -- that's rather confusing > > - does the return code of the backup not indicate the success or not of the > backup? > - will the backup end up not being succesful only if a specific list of return > codes are returned? > I've bumped the severity of this bug, because it sounds like it's not clear that Vorta assumes that a backup consists solely of $USER accessible paths, and this may result in the following case: 1. User adds / as a source 2. "backup successful" 3. Catastrophic system failure 4. Restoring from backup results in a broken Debian installation 5. User feels betrayed, Debian reputation for reliability suffers, trust in Vorta suffers. IMHO backup software reliability is like a file system reliability or anything email-related--unexpected behaviour or bugs that result in an incomplete dataset will prejudice the user against the software forever. To be fair, upstream is open about this limitation, but it sounds like it's not visible enough, and permission checks are--after all--a cornerstone of correct design ;-) Regards, Nicholas
signature.asc
Description: PGP signature
