| Age | Commit message (Collapse) | Author |
|---|
|
Update windows branch
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Added documentation for BORG_CONFIG_DIR
|
|
|
|
flake8: add some ignores
|
|
|
|
don't do stat() when not recursing into excluded dir, fixes #3209
|
|
add BORG_CONFIG_DIR env, fixes #3083
|
|
Clarify using a blank passphrase in keyfile mode
|
|
|
|
|
|
|
|
|
|
also: fix exception handling for the stat() calls
just moving all these lines into the "try"-block below (like it was in 1.0).
|
|
arg parsing: fix fallback function, refactor, fixes #3205
|
|
This is a fixup for #3155, which was broken on at least python <= 3.4.2.
Also clarify when to use which *func in set_defaults.
(cherry picked from commit 5ce4fa970413e3cedbc36e2f728863eaa69dad21)
|
|
fix server-side IndexError for 4-arg open() of old clients, fixes #3192
|
|
fix crash with relative BORG_KEY_FILE, fixes #3197
|
|
show excluded dir with "x" for tagged dirs / caches, fixes #3189
|
|
|
|
Add Nix/NixOS install command
|
|
|
|
borg 1.1(.0) server didn't support the 4 argument open() calls made
by < 1.0.7 clients.
|
|
|
|
remove hardlinked symlink warning, update docs
|
|
implement --nobsdflags and --exclude-nodump
|
|
do no read/archive bsdflags: borg create --nobsdflags ...
do not extract/set bsdflags: borg extract --nobsdflags ...
use cases:
- fs shows wrong / random bsdflags (bug in filesystem)
- fs does not support bsdflags anyway
- already archived bsdflags are wrong / unwanted
- borg shows any sort of unwanted effect due to get_flags, esp. on Linux
the nodump flag ("do not backup this file") is not honoured any more by
default because this functionality (esp. if it happened by error or
unexpected) was rather confusing and unexplainable at first to users.
if you want that "do not backup NODUMP-flagged files" behaviour, use:
borg create --exclude-nodump ...
|
|
the warning was annoying for people with a lot of such items and
they can not do anything about it anyway.
thus, just document this as a limitation.
|
|
cache: use SaveFile for more safety, fixes #3158
|
|
Looks like under unfortunate circumstances, these files could become
0 byte files (see #3158). SaveFile usage should prevent that.
|
|
borg recreate: correctly compute part file sizes, fixes #3157
|
|
when doing in-file checkpointing, borg creates *.borg_part_N files.
complete_file = part_1 + part_2 + ... + part_N
the source item for recreate already has a precomputed (total) size
member, thus we must force recomputation from the (partial) chunks
list to correct the size to be the part's size only.
borg create avoided this problem by computing the size member after
writing all the parts. this is now not required any more.
the bug is mostly cosmetic, borg check will complain, borg extract on
a part file would also complain. but all the complaints only refer to
the wrong metadata of the part files, the part files' contents are
correct.
usually you will never extract or look at part files, but only deal
with the full file, which will be completely valid, all metadata and
content.
you can get rid of the archives with these cosmetic errors by running
borg recreate on them with a fixed borg version. the old part files
will get dropped (because they are usually ignored) and any new part
file created due to checkpointing will be correct.
|
|
bsdflags support: skip blk/chr/lnk file type, fixes #3130
|
|
opening a device file for a non-existing device can be very slow.
symlinks will make the open() call fail as it is using O_NOFOLLOW.
also: lstat -> stat(..., follow_symlinks=False) like everywhere else.
|
|
move --no-files-cache from common to borg create options, fixes #3146
for borg prune, just use do_files=False (it only needs the chunks
cache, not the files cache).
|
|
don't crash if only a global option is given, show help, fixes #3142
|
|
don't brew update, hopefully fixes #2532
|
|
readme: -e is required in borg 1.1
|
|
|
|
|
|
|
|
|
|
logging with fileConfig: set json attr on "borg" logger, fixes #3114
|
