octoleo/restic
2
2
Fork 0
mirror of https://github.com/octoleo/restic.git synced 2024-12-22 10:58:55 +00:00
Code Issues Releases Wiki Activity

tweak changelogs

Browse Source
This commit is contained in:
Michael Eischer 2023-04-23 12:40:29 +02:00
parent f342db7666
commit 1e6e9f9bd0
6 changed files with 17 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
changelog/unreleased/issue-2260
View File

@ -1,9 +1,9 @@
Bugfix: Exotic filenames no longer break restic backup's status output 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 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, versions of restic, those names were printed without first sanitizing them,
so that filenames containing newlines or terminal control characters could so that filenames containing newlines or terminal control characters could
mess up restic backup's output or even change the state of a terminal. mangle the status output or even change the state of a terminal.
Filenames are now checked and quoted if they contain non-printable or Filenames are now checked and quoted if they contain non-printable or
non-Unicode characters. non-Unicode characters.

8
changelog/unreleased/issue-4211
View File

@ -1,8 +1,8 @@
Bugfix: Restic dump now interprets --host and --path correctly Bugfix: Make `dump` interpret --host and --path correctly
Restic dump previously confused its --host=<host> and --path=<path> A regression in restic 0.15.0 caused `dump` to confuse its `--host=<host>` and
options: it looked for snapshots with paths called <host> from hosts `--path=<path>` options: it looked for snapshots with paths called `<host>`
called <path>. It now treats the options as intended. from hosts called `<path>`. It now treats the options as intended.
https://github.com/restic/restic/issues/4211 https://github.com/restic/restic/issues/4211
https://github.com/restic/restic/pull/4212 https://github.com/restic/restic/pull/4212

6
changelog/unreleased/issue-4239
View File

@ -1,8 +1,8 @@
Bugfix: Correct number of blocks reported in mount point Bugfix: Correct number of blocks reported in mount point
Restic mount points incorrectly reported the number of 512-byte (POSIX Restic mount points reported and incorrect number of 512-byte (POSIX standard)
standard) blocks for files and links, due to a rounding bug. In particular, blocks for files and links due to a rounding bug. In particular, empty files
empty files were reported as taking one block instead of zero. were reported as taking one block instead of zero.
The rounding is now fixed: the number of blocks reported is the file size 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. (or link target size), divided by 512 and rounded up to a whole number.

13
changelog/unreleased/issue-4253
View File

@ -1,11 +1,10 @@
Bugfix: Mount command should no longer create spurious filesystem loops Bugfix: `mount` should no longer create spurious filesystem loops
When a backup contains a directory that has the same name as its parent, When a backup contains a directory that has the same name as its parent, say
say, a/b/b, and the GNU find command were run on this backup in a restic `a/b/b`, and the GNU `find` command were run on this backup in a restic mount,
mount, find command would refuse to traverse the lowest "b" directory, `find` would refuse to traverse the lowest `b` directory, instead printing
instead printing "File system loop detected". This is due to the way the `File system loop detected`. This is due to the way the restic mount command
restic mount command generates inode numbers for directories in the mount generates inode numbers for directories in the mount point.
point.
The rule for generating these inode numbers was changed in 0.15.0. It has 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, now been changed again to avoid this issue. A perfect rule does not exist,

2
changelog/unreleased/pull-4180
View File

@ -1,5 +1,5 @@
Enhancement: Add release binaries for riscv64 architecture on Linux Enhancement: Add release binaries for riscv64 architecture on Linux
We've added release binaries for riscv64 architecture on Linux. We've added release binaries for the riscv64 architecture on Linux.
https://github.com/restic/restic/pull/4180 https://github.com/restic/restic/pull/4180

2
changelog/unreleased/pull-4219
View File

@ -1,5 +1,5 @@
Enhancement: Upgrade Minio to 7.0.49 Enhancement: Upgrade Minio to 7.0.49
Upgraded to allow use of the ap-southeast-4 region (Melbourne) Upgraded to allow use of the ap-southeast-4 region (Melbourne).
https://github.com/restic/restic/pull/4219 https://github.com/restic/restic/pull/4219