-
-
Notifications
You must be signed in to change notification settings - Fork 729
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
BORG_EXIT_CODES=modern as DEFAULT in borg2? #8110
Comments
Vorta doesn't use them extensively right now. We could add better error messages after this is the default. Right now we only say "Some files couldn't be read, see logs for details" for example. |
@m3nu Thanks for the feedback! Just as a general note: support for these error/warning codes could be added at any time IF the wrapper checks/sets BORG_EXIT_CODES and reacts accordingly. This would be good, considering that borg >= 1.4 will already optionally support this (and will be released soon). |
Recent versions of borgmatic set |
@witten Thanks for the feedback. Just be careful: setting that will only change behaviour for borg >= 1.4. |
Understood! |
For 2.0 that's totally fine. |
borg 1.4 defaults to "legacy".
We could change that for borg2 to "modern", so borg by default gives a lot of specific error and warning exit codes.
Opinions about that?
The text was updated successfully, but these errors were encountered: