|
|
@@ -131,14 +131,15 @@ The best check that everything is ok is to run a dry-run extraction::
|
|
|
Changelog
|
|
|
=========
|
|
|
|
|
|
-Version 1.1.2 (2017-11-05)
|
|
|
---------------------------
|
|
|
+Version 1.1.3 (not released yet)
|
|
|
+--------------------------------
|
|
|
|
|
|
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
|
|
|
@@ -152,6 +153,65 @@ Compatibility notes:
|
|
|
|
|
|
Fixes:
|
|
|
|
|
|
+- XXX SECFIX XXX
|
|
|
+- crc32: deal with unaligned buffer, add tests - this broke borg on older ARM
|
|
|
+ CPUs that can not deal with unaligned 32bit memory accesses and raise a bus
|
|
|
+ error in such cases. the fix might also improve performance on some CPUs as
|
|
|
+ all 32bit memory accesses by the crc32 code are properly aligned now. #3317
|
|
|
+- mount: fixed support of --consider-part-files and do not show .borg_part_N
|
|
|
+ files by default in the mounted FUSE filesystem. #3347
|
|
|
+- fixed cache/repo timestamp inconsistency message, highlight that information
|
|
|
+ is obtained from security dir (deleting the cache will not bypass this error
|
|
|
+ in case the user knows this is a legitimate repo).
|
|
|
+- borgfs: don't show sub-command in borgfs help, #3287
|
|
|
+- create: show an error when --dry-run and --stats are used together, #3298
|
|
|
+
|
|
|
+New features:
|
|
|
+
|
|
|
+- mount: added exclusion group options and paths, #2138
|
|
|
+
|
|
|
+ Reused some code to support similar options/paths as borg extract offers -
|
|
|
+ making good use of these to only mount a smaller subset of dirs/files can
|
|
|
+ speed up mounting a lot and also will consume way less memory.
|
|
|
+
|
|
|
+ borg mount [options] repo_or_archive mountpoint path [paths...]
|
|
|
+
|
|
|
+ paths: you can just give some "root paths" (like for borg extract) to
|
|
|
+ only partially populate the FUSE filesystem.
|
|
|
+
|
|
|
+ new options: --exclude[-from], --pattern[s-from], --strip-components
|
|
|
+- create/extract: support st_birthtime on platforms supporting it, #3272
|
|
|
+- add "borg config" command for querying/setting/deleting config values, #3304
|
|
|
+
|
|
|
+Other changes:
|
|
|
+
|
|
|
+- clean up and simplify packaging (only package committed files, do not install
|
|
|
+ .c/.h/.pyx files)
|
|
|
+- docs:
|
|
|
+
|
|
|
+ - point out tuning options for borg create, #3239
|
|
|
+ - add instructions for using ntfsclone, zerofree, #81
|
|
|
+ - move image backup-related FAQ entries to a new page
|
|
|
+ - clarify key aliases for borg list --format, #3111
|
|
|
+ - mention break-lock in checkpointing FAQ entry, #3328
|
|
|
+ - document sshfs rename workaround, #3315
|
|
|
+ - add FAQ about removing files from existing archives
|
|
|
+ - add FAQ about different prune policies
|
|
|
+ - usage and man page for borgfs, #3216
|
|
|
+ - clarify create --stats duration vs. wall time, #3301
|
|
|
+ - clarify encrypted key format for borg key export, #3296
|
|
|
+ - update release checklist about security fixes
|
|
|
+ - document good and problematic option placements, fix examples, #3356
|
|
|
+ - add note about using --nobsdflags to avoid speed penalty related to
|
|
|
+ bsdflags, #3239
|
|
|
+ - move most of support section to www.borgbackup.org
|
|
|
+
|
|
|
+
|
|
|
+Version 1.1.2 (2017-11-05)
|
|
|
+--------------------------
|
|
|
+
|
|
|
+Fixes:
|
|
|
+
|
|
|
- fix KeyError crash when talking to borg server < 1.0.7, #3244
|
|
|
- extract: set bsdflags last (include immutable flag), #3263
|
|
|
- create: don't do stat() call on excluded-norecurse directory, fix exception
|
|
|
@@ -246,6 +306,19 @@ Other changes:
|
|
|
Version 1.1.0 (2017-10-07)
|
|
|
--------------------------
|
|
|
|
|
|
+Compatibility notes:
|
|
|
+
|
|
|
+- borg command line: do not put options in between positional arguments
|
|
|
+
|
|
|
+ This sometimes works (e.g. it worked in borg 1.0.x), but can easily stop
|
|
|
+ working if we make positional arguments optional (like it happened for
|
|
|
+ borg create's "paths" argument in 1.1). There are also places in borg 1.0
|
|
|
+ where we do that, so it doesn't work there in general either. #3356
|
|
|
+
|
|
|
+ Good: borg create -v --stats repo::archive path
|
|
|
+ Good: borg create repo::archive path -v --stats
|
|
|
+ Bad: borg create repo::archive -v --stats path
|
|
|
+
|
|
|
Fixes:
|
|
|
|
|
|
- fix LD_LIBRARY_PATH restoration for subprocesses, #3077
|
TW