From 5d658f216c1c8f9e53c8be65c703df046a1bc834 Mon Sep 17 00:00:00 2001 From: "Leo R. Lundgren" Date: Sat, 31 Aug 2024 17:28:24 +0200 Subject: [PATCH] doc: Polish unreleased changelogs --- changelog/unreleased/issue-2004 | 9 ++++----- changelog/unreleased/issue-4934 | 3 ++- changelog/unreleased/issue-4944 | 4 ++-- changelog/unreleased/issue-4945 | 2 +- changelog/unreleased/issue-4957 | 4 +--- changelog/unreleased/issue-4969 | 2 +- changelog/unreleased/issue-4970 | 3 ++- changelog/unreleased/issue-4975 | 2 +- changelog/unreleased/issue-5004 | 2 +- changelog/unreleased/issue-5005 | 2 +- changelog/unreleased/pull-4958 | 6 +++--- changelog/unreleased/pull-4977 | 2 +- changelog/unreleased/pull-4980 | 2 +- changelog/unreleased/pull-5018 | 2 +- 14 files changed, 22 insertions(+), 23 deletions(-) diff --git a/changelog/unreleased/issue-2004 b/changelog/unreleased/issue-2004 index a15651d75..5372eeb8c 100644 --- a/changelog/unreleased/issue-2004 +++ b/changelog/unreleased/issue-2004 @@ -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 : -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 : 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 diff --git a/changelog/unreleased/issue-4934 b/changelog/unreleased/issue-4934 index 56e22ad28..df77109a7 100644 --- a/changelog/unreleased/issue-4934 +++ b/changelog/unreleased/issue-4934 @@ -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 diff --git a/changelog/unreleased/issue-4944 b/changelog/unreleased/issue-4944 index 738da8e57..95ae24c03 100644 --- a/changelog/unreleased/issue-4944 +++ b/changelog/unreleased/issue-4944 @@ -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. diff --git a/changelog/unreleased/issue-4945 b/changelog/unreleased/issue-4945 index 024b30b21..a7a483fed 100644 --- a/changelog/unreleased/issue-4945 +++ b/changelog/unreleased/issue-4945 @@ -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 diff --git a/changelog/unreleased/issue-4957 b/changelog/unreleased/issue-4957 index 5da7463ae..59c73b5c7 100644 --- a/changelog/unreleased/issue-4957 +++ b/changelog/unreleased/issue-4957 @@ -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 diff --git a/changelog/unreleased/issue-4969 b/changelog/unreleased/issue-4969 index 9015c2eab..d92392a20 100644 --- a/changelog/unreleased/issue-4969 +++ b/changelog/unreleased/issue-4969 @@ -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 diff --git a/changelog/unreleased/issue-4970 b/changelog/unreleased/issue-4970 index 2fc9300c9..422ae3c25 100644 --- a/changelog/unreleased/issue-4970 +++ b/changelog/unreleased/issue-4970 @@ -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 diff --git a/changelog/unreleased/issue-4975 b/changelog/unreleased/issue-4975 index 2503f46da..614642c06 100644 --- a/changelog/unreleased/issue-4975 +++ b/changelog/unreleased/issue-4975 @@ -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 diff --git a/changelog/unreleased/issue-5004 b/changelog/unreleased/issue-5004 index a0df9478e..72e98a9a4 100644 --- a/changelog/unreleased/issue-5004 +++ b/changelog/unreleased/issue-5004 @@ -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 diff --git a/changelog/unreleased/issue-5005 b/changelog/unreleased/issue-5005 index eb712b967..16ac83b4a 100644 --- a/changelog/unreleased/issue-5005 +++ b/changelog/unreleased/issue-5005 @@ -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 ``` -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. diff --git a/changelog/unreleased/pull-4958 b/changelog/unreleased/pull-4958 index 02574ad33..dae9b2c8e 100644 --- a/changelog/unreleased/pull-4958 +++ b/changelog/unreleased/pull-4958 @@ -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 diff --git a/changelog/unreleased/pull-4977 b/changelog/unreleased/pull-4977 index 85e4091c5..781576a56 100644 --- a/changelog/unreleased/pull-4977 +++ b/changelog/unreleased/pull-4977 @@ -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. diff --git a/changelog/unreleased/pull-4980 b/changelog/unreleased/pull-4980 index 4b1de54bf..b51ee8d59 100644 --- a/changelog/unreleased/pull-4980 +++ b/changelog/unreleased/pull-4980 @@ -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 diff --git a/changelog/unreleased/pull-5018 b/changelog/unreleased/pull-5018 index 84f36355c..ca600c3e1 100644 --- a/changelog/unreleased/pull-5018 +++ b/changelog/unreleased/pull-5018 @@ -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