Dan Helfman
Dan Helfman
Recent versions of borgmatic set `BORG_EXIT_CODES=modern` unconditionally, so this proposed change to Borg 2 would be fine from borgmatic's perspective.
Understood!
borgmatic already supports Borg 2, but the big challenge for most docker-borgmatic users will be transferring their old Borg 1.x repo to 2.x: https://torsion.org/borgmatic/docs/how-to/upgrade/#borg-1.2-to-2.0 I don't see any reason why...
I don't think there's currently an image with Borg 2 inside. If you wanted to just do that for testing purposes, you could probably run the existing image and then...
Totally understood. Note that 2.0 at this point is _not_ recommended for production use, so it'll probably be a little while before it appears in the Docker container.
Thanks for taking the time to submit this! I like the general idea of formalizing our community's code of conduct. A couple of thoughts: * Is there a reason you...
That would be great.. Thank you for your flexibility here!
The ulimit thing may no longer be an issue in Podman 4.5.0+: https://github.com/containers/podman/pull/18078
This year I unfortunately won't have time to be a dedicated mentor, but I'd be happy to be on point for borgmatic PRs. Also, some of the borgmatic GSoC ideas...
> Alright, so I would need one more mentor in Google's system to get started. Done!