-
Notifications
You must be signed in to change notification settings - Fork 79
Restic v0.12.0 #74
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
Comments
I would suggest to test what is described here: restic/restic#2706 (comment) |
Seeing this ticket restic/restic#2739 I wonder if using |
Thanks for these thoughts. I am busy struggling to get the armv7 build running again. Not sure if we can release the update first and then implement your ideas in a minor release? |
Agreed. The aspects are just ideas for improvement and no breaking changes. Btw I feel it makes a lot of sense to get into a rhythm of always tracking new restic versions by creating an issue like this one. On another thought: I would like to engage with the restic community more. The ideal constellation would be to be the number 1 endorsed docker solution for restic. At this point it would also be easier to e.g. implement failure detection in cooperation with the restic core development |
As a user of |
@svenfoo It is already in master and in the |
Thanks for pointing that out, I got it up and running on the Raspberry Pi. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
https://github.com/restic/restic/releases/tag/v0.12.0
Hey all,
this is a ticket to
Linked to #73
Let's discuss
The text was updated successfully, but these errors were encountered: