From 2ce485063fb03a41ffc3abb0091bb2ac8444af07 Mon Sep 17 00:00:00 2001 From: Michael Eischer Date: Tue, 22 Oct 2024 19:47:44 +0200 Subject: [PATCH] polish changelogs --- changelog/unreleased/issue-4004 | 16 ++++++++-------- changelog/unreleased/issue-5050 | 6 +++--- changelog/unreleased/issue-5063 | 7 ++++--- changelog/unreleased/pull-5047 | 9 +++++---- changelog/unreleased/pull-5057 | 24 +++++++++++++----------- 5 files changed, 33 insertions(+), 29 deletions(-) diff --git a/changelog/unreleased/issue-4004 b/changelog/unreleased/issue-4004 index ca23af26f..d95ad02e9 100644 --- a/changelog/unreleased/issue-4004 +++ b/changelog/unreleased/issue-4004 @@ -1,12 +1,12 @@ -Bugfix: Allow use of container level SAS/SAT tokens with Azure backend +Bugfix: Support container-level SAS/SAT tokens for Azure backend -When using a SAS/SAT token for authentication with Azure, restic was expecting -the provided token to be generated at the account level, granting permissions -to the storage account and all its containers. This caused an error that did -not allow tokens that were generated at the container level to be used to -initalize a repository. -Restic now allows SAS/SAT tokens that were generated at the account or -container level to be used to initalize a repository. +Restic previously expected SAS/SAT tokens to be generated at the account level, +which prevented tokens created at the container level from being used to +initialize a repository. This caused an error when attempting to initialize a +repository with container-level tokens. + +Restic now supports both account-level and container-level SAS/SAT tokens for +initializing a repository. https://github.com/restic/restic/issues/4004 https://github.com/restic/restic/pull/5093 diff --git a/changelog/unreleased/issue-5050 b/changelog/unreleased/issue-5050 index 9604fc857..ba736e4db 100644 --- a/changelog/unreleased/issue-5050 +++ b/changelog/unreleased/issue-5050 @@ -1,7 +1,7 @@ -Bugfix: Missing error if `tag` fails to lock repository +Bugfix: Return error if `tag` fails to lock repository -Since restic 0.17.0, the `tag` command did not return an error if it failed to -open or lock the repository. This has been fixed. +Since restic 0.17.0, the `tag` command did not return an error when it failed +to open or lock the repository. This issue has been fixed. https://github.com/restic/restic/issues/5050 https://github.com/restic/restic/pull/5056 diff --git a/changelog/unreleased/issue-5063 b/changelog/unreleased/issue-5063 index 65aa379e4..63e26fe61 100644 --- a/changelog/unreleased/issue-5063 +++ b/changelog/unreleased/issue-5063 @@ -1,8 +1,9 @@ Bugfix: Correctly `backup` extended metadata when using VSS on Windows -On Windows, when creating a backup using the `--use-fs-snapshot` option, -then the extended metadata was not read from the filesystem snapshot. This -could result in errors when files have been removed in the meantime. +On Windows, when creating a backup with the `--use-fs-snapshot` option, restic +read extended metadata from the original filesystem path instead of from the +snapshot. This could result in errors if files were removed during the backup +process. This issue has been resolved. diff --git a/changelog/unreleased/pull-5047 b/changelog/unreleased/pull-5047 index ee50c6ec7..ace02c3b4 100644 --- a/changelog/unreleased/pull-5047 +++ b/changelog/unreleased/pull-5047 @@ -1,7 +1,8 @@ -Bugfix: Fix possible error on concurrent cache cleanup +Bugfix: Resolve potential error during concurrent cache cleanup -Fix for multiple restic processes executing concurrently and racing to -remove obsolete snapshots from the local backend cache. Restic now suppresses the `no -such file or directory` error. +When multiple restic processes ran concurrently, they could compete to remove +obsolete snapshots from the local backend cache, sometimes leading to a "no +such file or directory" error. Restic now suppresses this error to prevent +issues during cache cleanup. https://github.com/restic/restic/pull/5047 diff --git a/changelog/unreleased/pull-5057 b/changelog/unreleased/pull-5057 index c34436044..99df31d2b 100644 --- a/changelog/unreleased/pull-5057 +++ b/changelog/unreleased/pull-5057 @@ -1,21 +1,23 @@ -Bugfix: Do not include irregular files in backup +Bugfix: Exclude irregular files from backups -Since restic 0.17.1, files with type `irregular` could incorrectly be included -in snapshots. This is most likely to occur when backing up special file types -on Windows that cannot be handled by restic. +Since restic 0.17.1, files with the type irregular could mistakenly be included +in snapshots, especially when backing up special file types on Windows that +restic cannot process. This issue has been fixed. -This has been fixed. - -When running the `check` command this bug resulted in an error like the -following: +Previously, this bug caused the `check` command to report errors like the +following one: ``` tree 12345678[...]: node "example.zip" with invalid type "irregular" ``` -Repairing the affected snapshots requires upgrading to restic 0.17.2 and then -manually running `restic repair snapshots --forget`. This will remove the -`irregular` files from the snapshots. +To repair affected snapshots, upgrade to restic 0.17.2 and run: + +``` +restic repair snapshots --forget +``` + +This will remove the `irregular` files from the snapshots. https://github.com/restic/restic/pull/5057 https://forum.restic.net/t/errors-found-by-check-1-invalid-type-irregular-2-ciphertext-verification-failed/8447/2