TW
I am not familiar with freebsd and ACLs on freebsd, so it would be good if a freebsd user / developer could help with this.
Workaround for freebsd 13 borg users: use borg 1.2.x for now.
@mandree If you use freebsd and know about that stuff, can you fix the freebsd platform code in borg in a PR?
@mandree Hmm, maybe it would be easier to just use api calls that are also present on freebsd13? I wasn't even aware that I am using something that new when...
Note: This needs a PR from some freebsd user/developer to fix the borg acl code so it is freebsd 13 compatible. The fix should be to use only api calls...
@mikae1 yes, that should work. Just make sure to use borg >= 1.2.5 (see the upgrade / CVE notes at the top of the changelog), using borg clients = 1.2.5...
Yes, that should also work.
Note: freebsd 13 will be EOL in May 2026.
Closing this. EOL soon, fbsd13 users can use borg 1.2.x.
@edsonsbj That's a big no-no in a script: ``` borg break-lock $BORG_REPO ``` From the docs: Please use carefully and only while no borg process (on any machine) is trying...