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

BORG_EXIT_CODES=modern as DEFAULT in borg2? #8110

Open
ThomasWaldmann opened this issue Feb 20, 2024 · 7 comments
Open

BORG_EXIT_CODES=modern as DEFAULT in borg2? #8110

ThomasWaldmann opened this issue Feb 20, 2024 · 7 comments
Milestone

Comments

@ThomasWaldmann
Copy link
Member

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?

@ThomasWaldmann ThomasWaldmann added this to the 2.0.0rc1 milestone Feb 20, 2024
@ThomasWaldmann
Copy link
Member Author

@m3nu @witten @sophie-h

@m3nu
Copy link
Contributor

m3nu commented Feb 20, 2024

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.

@ThomasWaldmann
Copy link
Member Author

ThomasWaldmann commented Feb 20, 2024

@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).

@witten
Copy link
Contributor

witten commented Feb 20, 2024

Recent versions of borgmatic set BORG_EXIT_CODES=modern unconditionally, so this proposed change to Borg 2 would be fine from borgmatic's perspective.

@ThomasWaldmann
Copy link
Member Author

@witten Thanks for the feedback.

Just be careful: setting that will only change behaviour for borg >= 1.4.

@witten
Copy link
Contributor

witten commented Feb 20, 2024

Understood!

@sophie-h
Copy link
Contributor

Opinions about that?

For 2.0 that's totally fine.

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

No branches or pull requests

4 participants