TrueCloudLab/restic
16
0
Fork 2
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

doc: Polish unreleased changelogs

Browse source
This commit is contained in:
Leo R. Lundgren 2024-08-31 17:28:24 +02:00
parent 7b0b9539b1
commit 5d658f216c
14 changed files with 22 additions and 23 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
changelog/unreleased/issue-2004
View file

@ -5,11 +5,10 @@ name without a trailing slash, for example, `C:`, then restoring the
resulting snapshot would result in an error. Note that using `C:\`
as backup target worked correctly.
Specifying volume names is now handled correctly.
To restore snapshots created before this bugfix, use the <snapshot>:<subpath>
syntax. For example, to restore a snapshot with ID `12345678` that backed up
`C:`, use the following command:
Specifying volume names is now handled correctly. To restore snapshots
created before this bugfix, use the <snapshot>:<subpath> syntax. For
example, to restore a snapshot with ID `12345678` that backed up `C:`,
use the following command:
```
restic restore 12345678:/C/C:./ --target output/folder

3
changelog/unreleased/issue-4934
View file

@ -4,7 +4,8 @@ Previously, restic only removed snapshots from the cache on the host where the
`forget` command was executed. On other hosts that use the same repository, the
old snapshots remained in the cache.
Restic now automatically clears old snapshots from the local cache of the current host.
Restic now automatically clears old snapshots from the local cache of the
current host.
https://github.com/restic/restic/issues/4934
https://github.com/restic/restic/pull/4981

4
changelog/unreleased/issue-4944
View file

@ -1,7 +1,7 @@
Enhancement: Print JSON-formatted errors during `restore --json`
Restic printed any `restore` errors directly to the console as freeform text
messages, even when using the `--json` option.
Restic used to print any `restore` errors directly to the console as freeform
text messages, even when using the `--json` option.
Now, when `--json` is specified, restic prints them as JSON formatted messages.

2
changelog/unreleased/issue-4945
View file

@ -4,7 +4,7 @@ Previously, when running a backup with the `--json` option, restic failed to
include the actual error message in the output, resulting in `"error": {}`
being displayed.
Restic now includes the error text in JSON output.
This has now been fixed, and restic now includes the error text in JSON output.
https://github.com/restic/restic/issues/4945
https://github.com/restic/restic/pull/4946

4
changelog/unreleased/issue-4957
View file

@ -2,9 +2,7 @@ Bugfix: Fix delayed cancellation of certain commands
Since restic 0.17.0, some commands did not immediately respond to cancellation
via Ctrl-C (SIGINT) and continued running for a short period. The most affected
commands were `diff`,`find`, `ls`, `stats` and `rewrite`.
This has been fixed.
commands were `diff`,`find`, `ls`, `stats` and `rewrite`. This is now resolved.
https://github.com/restic/restic/issues/4957
https://github.com/restic/restic/pull/4960

2
changelog/unreleased/issue-4969
View file

@ -1,7 +1,7 @@
Bugfix: Correctly restore timestamp for files with resource forks on macOS
On macOS, timestamps were not restored for files with resource forks. This has
been fixed.
now been fixed.
https://github.com/restic/restic/issues/4969
https://github.com/restic/restic/pull/5006

3
changelog/unreleased/issue-4970
View file

@ -8,7 +8,8 @@ error:
`List(data) returned error, retrying after 1s: [...]: request timeout`
It is now possible to increase the timeout using the `--stuck-request-timeout` option.
It is now possible to increase the timeout using the `--stuck-request-timeout`
option.
https://github.com/restic/restic/issues/4970
https://github.com/restic/restic/pull/5014

2
changelog/unreleased/issue-4975
View file

@ -1,7 +1,7 @@
Bugfix: Prevent `backup --stdin-from-command` from panicking
Restic would previously crash if `--stdin-from-command` was specified without
providing a command. This issue has been fixed.
providing a command. This issue has now been fixed.
https://github.com/restic/restic/issues/4975
https://github.com/restic/restic/pull/4976

2
changelog/unreleased/issue-5004
View file

@ -6,7 +6,7 @@ On Windows, creating a backup could sometimes trigger the following error:
error: nodeFromFileInfo [...]: get named security info failed with: a required privilege is not held by the client.
```
This has been fixed.
This has now been fixed.
https://github.com/restic/restic/issues/5004
https://github.com/restic/restic/pull/5019

2
changelog/unreleased/issue-5005
View file

@ -7,7 +7,7 @@ the lock files failed to load, resulting in the error:
unable to create lock in backend: circuit breaker open for file <lock/1234567890>
```
This issue has been addressed. The error handling now properly retries the
This issue has now been addressed. The error handling now properly retries the
locking operation. In addition, restic waits a few seconds between locking
retries to increase chances of successful locking.

6
changelog/unreleased/pull-4958
View file

@ -1,7 +1,7 @@
Bugfix: Don't ignore metadata-setting errors during restore
Restic ignored errors when setting timestamps, attributes, or file modes during
a restore. It now reports those, except for permission errors when running
without root privileges.
Previously, restic used to ignore errors when setting timestamps, attributes,
or file modes during a restore. It now reports those errors, except for
permission related errors when running without root privileges.
https://github.com/restic/restic/pull/4958

2
changelog/unreleased/pull-4977
View file

@ -1,4 +1,4 @@
Change: `backup` includes files with incomplete metadata
Change: Also back up files with incomplete metadata
If restic failed to read extended metadata for a file or folder during a
backup, then the file or folder was not included in the resulting snapshot.

2
changelog/unreleased/pull-4980
View file

@ -1,6 +1,6 @@
Bugfix: Skip extended attribute processing on unsupported Windows volumes
For restic 0.17.0, backups of certain Windows paths, such as network drives,
With restic 0.17.0, backups of certain Windows paths, such as network drives,
failed due to errors while fetching extended attributes.
Restic now skips extended attribute processing for volumes where they are not

2
changelog/unreleased/pull-5018
View file

@ -7,7 +7,7 @@ use by the client, it could result in the following error:
http2: Transport: cannot retry err [http2: Transport received Server's graceful shutdown GOAWAY] after Request.Body was written; define Request.GetBody to avoid this error
```
This issue has been resolved.
This issue has now been resolved.
https://github.com/restic/restic/pull/5018
https://forum.restic.net/t/receiving-http2-goaway-messages-with-windows-restic-v0-17-0/8367