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

doc: Polish changelogs

Browse Source
This commit is contained in:
Leo R. Lundgren 2023-04-23 22:09:52 +02:00
parent 1e6e9f9bd0
commit 0bac935dac
7 changed files with 16 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
changelog/unreleased/issue-2260
View File

@ -1,9 +1,8 @@
Bugfix: Exotic filenames no longer break restic backup's status output Bugfix: Sanitize filenames printed by `backup` during processing
Restic `backup` shows the names of files that it is working on. In previous The `backup` command would previously not sanitize the filenames it printed
versions of restic, those names were printed without first sanitizing them, during processing, potentially causing newlines or terminal control characters
so that filenames containing newlines or terminal control characters could to mangle the status 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.

2
changelog/unreleased/issue-4211
View File

@ -1,4 +1,4 @@
Bugfix: Make `dump` interpret --host and --path correctly Bugfix: Make `dump` interpret `--host` and `--path` correctly
A regression in restic 0.15.0 caused `dump` to confuse its `--host=<host>` and A regression in restic 0.15.0 caused `dump` to confuse its `--host=<host>` and
`--path=<path>` options: it looked for snapshots with paths called `<host>` `--path=<path>` options: it looked for snapshots with paths called `<host>`

4
changelog/unreleased/issue-4239
View File

@ -1,11 +1,11 @@
Bugfix: Correct number of blocks reported in mount point Bugfix: Correct number of blocks reported in mount point
Restic mount points reported and incorrect number of 512-byte (POSIX standard) Restic mount points reported an incorrect number of 512-byte (POSIX standard)
blocks for files and links due to a rounding bug. In particular, empty files blocks for files and links due to a rounding bug. In particular, 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.
https://github.com/restic/restic/issues/4239 https://github.com/restic/restic/issues/4239
https://github.com/restic/restic/pull/4240 https://github.com/restic/restic/pull/4240

7
changelog/unreleased/issue-4253
View File

@ -1,14 +1,15 @@
Bugfix: `mount` should no longer create spurious filesystem loops Bugfix: Minimize risk of spurious filesystem loops with `mount`
When a backup contains a directory that has the same name as its parent, say 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, `a/b/b`, and the GNU `find` command was run on this backup in a restic mount,
`find` would refuse to traverse the lowest `b` directory, instead printing `find` would refuse to traverse the lowest `b` directory, instead printing
`File system loop detected`. This is due to the way the restic mount command `File system loop detected`. This was due to the way the restic mount command
generates inode numbers for directories in the mount point. generates inode numbers for directories in the mount 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,
but the probability of this behavior occurring is now extremely small. 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 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 the mount point should work as long as they don't rely on inode numbers for
detecting filesystem loops. detecting filesystem loops.

2
changelog/unreleased/issue-4275
View File

@ -1,4 +1,4 @@
Security: Update golang.org/x/net to address CVE-2022-41723 Security: Update golang.org/x/net to address CVE-2022-41723
https://github.com/restic/restic/issues/4275 https://github.com/restic/restic/issues/4275
https://github.com/restic/restic/pull/4213 https://github.com/restic/restic/pull/4213

3
changelog/unreleased/pull-4180
View File

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

4
changelog/unreleased/pull-4219
View File

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