Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refuse to add inaccessible folders, warn on inaccessible files during backup #951

Merged
merged 5 commits into from
Apr 21, 2021

Conversation

m3nu
Copy link
Contributor

@m3nu m3nu commented Apr 17, 2021

We now refuse to add unreadable folders and .

warn about access errors during backup

Fixes #916 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987074)

Comment on lines 35 to 36
if result['returncode'] == 1:
self.app.backup_progress_event.emit(self.tr('Backup finished. Some files were not accessible.'))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure that this is correct, because doesn't borg use returncode=1 as a catch-all for a variety of errors?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right. Could also be "Backup finished with warnings. See logs for details."

Upside is it's more "correct". Downside is that the large majority of warnings will be access errors. Can't think of other warnings I've seen. That fact is now hidden in the logs.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've added a separate issue #952 to nag Mac users about Full Disk access. This should make such errors very rare and we can use the vague sentence. "Backup finished with warnings. See logs for details."

OK?

Copy link
Contributor Author

@m3nu m3nu Apr 18, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've now merged the feature to nag Mac users about proper permissions. Mostly due to a overwhelming response on Twitter: https://twitter.com/borg_base/status/1383302657045979144

With this, access errors would be fairly rare everywhere and the more vague sentence should be fine.

@m3nu m3nu merged commit 0e91775 into borgbase:master Apr 21, 2021
@m3nu m3nu deleted the issue/916/source-permissions branch April 21, 2021 07:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Verify permissions when adding a new source file or folder
2 participants