Overview
Request 704975 accepted
- Update to version 1.1.10 (2019-05-16)
+ Compatibility notes:
* When upgrading from borg 1.0.x to 1.1.x, please note:
* read all the compatibility notes for 1.1.0*, starting from
1.1.0b1.
* borg upgrade: you do not need to and you also should not run
it.
* borg might ask some security-related questions once after
upgrading. You can answer them either manually or via
environment variable. One known case is if you use
unencrypted repositories, then it will ask about a unknown
unencrypted repository one time.
* your first backup with 1.1.x might be significantly slower
(it might completely read, chunk, hash a lot files) - this is
due to the --files-cache mode change (and happens every time
you change mode). You can avoid the one-time slowdown by
using the pre-1.1.0rc4-compatible mode (but that is less safe
for detecting changed files than the default). See the
--files-cache docs for details.
+ Fixes:
* extract: hang on partial extraction with ssh: repo, when
hardlink master is not matched/extracted and borg hangs on
related slave hardlink, #4350
* lrucache: regularly remove old FDs, #4427
* avoid stale filehandle issues, #3265
* freebsd: make xattr platform code api compatible with linux,
#3952
* use whitelist approach for borg serve, #4097
* borg command shall terminate with rc 2 for ImportErrors,
#4424
Request History
frispete created request
- Update to version 1.1.10 (2019-05-16)
+ Compatibility notes:
* When upgrading from borg 1.0.x to 1.1.x, please note:
* read all the compatibility notes for 1.1.0*, starting from
1.1.0b1.
* borg upgrade: you do not need to and you also should not run
it.
* borg might ask some security-related questions once after
upgrading. You can answer them either manually or via
environment variable. One known case is if you use
unencrypted repositories, then it will ask about a unknown
unencrypted repository one time.
* your first backup with 1.1.x might be significantly slower
(it might completely read, chunk, hash a lot files) - this is
due to the --files-cache mode change (and happens every time
you change mode). You can avoid the one-time slowdown by
using the pre-1.1.0rc4-compatible mode (but that is less safe
for detecting changed files than the default). See the
--files-cache docs for details.
+ Fixes:
* extract: hang on partial extraction with ssh: repo, when
hardlink master is not matched/extracted and borg hangs on
related slave hardlink, #4350
* lrucache: regularly remove old FDs, #4427
* avoid stale filehandle issues, #3265
* freebsd: make xattr platform code api compatible with linux,
#3952
* use whitelist approach for borg serve, #4097
* borg command shall terminate with rc 2 for ImportErrors,
#4424
frispete accepted request