TW
Well, it looked pretty similar to the top post. borg 1.4 and master are using more modern tooling, I just wanted to do a final 1.2.9 release with as little...
When reading backup source files, borg calls `OsOpen` (which is a wrapper around `os.open`), resulting in a OS-level file handle (int), called `fd` or `dir_fd` in the code.
- Guess `set | grep BORG_` would also solve this. - I think we usually have cli arguments taking precedence over env vars.
There are 2 ways to exclude: - `-` will not backup matching files, but will still recurse into the excluded directory (use this if you want to include some stuff...
BTW, if you do not use `!`, borg will trigger the auto-mounting while recursing - is that what you want?
Well, then try using `! re:^mnt` or so, so that it matches on the mnt directory name already and does not recurse into mnt and does not trigger your automounter.
The explanation for that is your automounter: it changes the inode in the moment borg accesses the mountpoint directory name. `-` doing recursion and `!` not doing recursion is documented...
For the borg1 to borg2 transfer, the passphrase issue can be avoided by just using the same passphrase for the new repo. It can be changed after the transfer is...
I am also having this issue in my macOS 10.12 platform testing VM. pip 24.1 works, so this is a regression. https://github.com/borgbackup/borg/issues/8415
Would be cool if this could get fixed soon. It broke the `borgbackup` macOS platform testing / binary building (which intentionally uses an older macOS so the binary works on...