github/restic
4
0 Fork 0
mirror of https://github.com/restic/restic.git synced 2026-11-13 14:42:03 +00:00
Code Issues Releases Wiki Activity

Merge branch 'patch-release'

Browse Source
This commit is contained in:
Michael Eischer committed 2023-04-24 20:44:38 +02:00
2 parents 41cc320145 ac7ac0cb97
commit c8641f4479
42 files changed
+168 -75
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

changelog/unreleased/issue-2260
-13
View File
@@ -1,13 +0,0 @@
Bugfix: Exotic filenames no longer break restic backup's status output
Restic backup shows the names of files that it is working on. In previous
versions of restic, those names were printed without first sanitizing them,
so that filenames containing newlines or terminal control characters could
mess up restic backup's output or even change the state of a terminal.
Filenames are now checked and quoted if they contain non-printable or
non-Unicode characters.
https://github.com/restic/restic/issues/2260
https://github.com/restic/restic/issues/4191
https://github.com/restic/restic/pull/4192
changelog/unreleased/issue-4211
-8
View File
@@ -1,8 +0,0 @@
Bugfix: Restic dump now interprets --host and --path correctly
Restic dump previously confused its --host=<host> and --path=<path>
options: it looked for snapshots with paths called <host> from hosts
called <path>. It now treats the options as intended.
https://github.com/restic/restic/issues/4211
https://github.com/restic/restic/pull/4212
changelog/unreleased/issue-4239
-11
View File
@@ -1,11 +0,0 @@
Bugfix: Correct number of blocks reported in mount point
Restic mount points incorrectly reported the number of 512-byte (POSIX
standard) blocks for files and links, due to a rounding bug. In particular,
empty files were reported as taking one block instead of zero.
The rounding is now fixed: the number of blocks reported is the file size
(or link target size), divided by 512 and rounded up to a whole number.
https://github.com/restic/restic/issues/4239
https://github.com/restic/restic/pull/4240
changelog/unreleased/issue-4253
-18
View File
@@ -1,18 +0,0 @@
Bugfix: Mount command should no longer create spurious filesystem loops
When a backup contains a directory that has the same name as its parent,
say, a/b/b, and the GNU find command were run on this backup in a restic
mount, find command would refuse to traverse the lowest "b" directory,
instead printing "File system loop detected". This is due to the way the
restic mount command generates inode numbers for directories in the mount
point.
The rule for generating these inode numbers was changed in 0.15.0. It has
now been changed again to avoid this issue. A perfect rule does not exist,
but the probability of this behavior occurring is now extremely small.
When it does occur, the mount point is not broken, and scripts that traverse
the mount point should work as long as they don't rely on inode numbers for
detecting filesystem loops.
https://github.com/restic/restic/issues/4253
https://github.com/restic/restic/pull/4255
changelog/unreleased/pull-4180
-5
View File
@@ -1,5 +0,0 @@
Enhancement: Add release binaries for riscv64 architecture on Linux
We've added release binaries for riscv64 architecture on Linux.
https://github.com/restic/restic/pull/4180
changelog/unreleased/pull-4219
-5
View File
@@ -1,5 +0,0 @@
Enhancement: Upgrade Minio to 7.0.49
Upgraded to allow use of the ap-southeast-4 region (Melbourne)
https://github.com/restic/restic/pull/4219