KurlesHS/restic
1
0
Fork 0
forked from TrueCloudLab/restic
Code Pull requests Activity

polish changelogs

Browse source
This commit is contained in:
Michael Eischer 2024-10-22 19:47:44 +02:00
parent f72febb34f
commit 2ce485063f
5 changed files with 33 additions and 29 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
changelog/unreleased/issue-4004
View file

@ -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 Restic previously expected SAS/SAT tokens to be generated at the account level,
the provided token to be generated at the account level, granting permissions which prevented tokens created at the container level from being used to
to the storage account and all its containers. This caused an error that did initialize a repository. This caused an error when attempting to initialize a
not allow tokens that were generated at the container level to be used to repository with container-level tokens.
initalize a repository.
Restic now allows SAS/SAT tokens that were generated at the account or Restic now supports both account-level and container-level SAS/SAT tokens for
container level to be used to initalize a repository. initializing a repository.
https://github.com/restic/restic/issues/4004 https://github.com/restic/restic/issues/4004
https://github.com/restic/restic/pull/5093 https://github.com/restic/restic/pull/5093

6
changelog/unreleased/issue-5050
View file

@ -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 Since restic 0.17.0, the `tag` command did not return an error when it failed
open or lock the repository. This has been fixed. to open or lock the repository. This issue has been fixed.
https://github.com/restic/restic/issues/5050 https://github.com/restic/restic/issues/5050
https://github.com/restic/restic/pull/5056 https://github.com/restic/restic/pull/5056

7
changelog/unreleased/issue-5063
View file

@ -1,8 +1,9 @@
Bugfix: Correctly `backup` extended metadata when using VSS on Windows Bugfix: Correctly `backup` extended metadata when using VSS on Windows
On Windows, when creating a backup using the `--use-fs-snapshot` option, On Windows, when creating a backup with the `--use-fs-snapshot` option, restic
then the extended metadata was not read from the filesystem snapshot. This read extended metadata from the original filesystem path instead of from the
could result in errors when files have been removed in the meantime. snapshot. This could result in errors if files were removed during the backup
process.
This issue has been resolved. This issue has been resolved.

9
changelog/unreleased/pull-5047
View file

@ -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 When multiple restic processes ran concurrently, they could compete to remove
remove obsolete snapshots from the local backend cache. Restic now suppresses the `no obsolete snapshots from the local backend cache, sometimes leading to a "no
such file or directory` error. such file or directory" error. Restic now suppresses this error to prevent
issues during cache cleanup.
https://github.com/restic/restic/pull/5047 https://github.com/restic/restic/pull/5047

24
changelog/unreleased/pull-5057
View file

@ -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 Since restic 0.17.1, files with the type irregular could mistakenly be included
in snapshots. This is most likely to occur when backing up special file types in snapshots, especially when backing up special file types on Windows that
on Windows that cannot be handled by restic. restic cannot process. This issue has been fixed.
This has been fixed. Previously, this bug caused the `check` command to report errors like the
following one:
When running the `check` command this bug resulted in an error like the
following:
``` ```
tree 12345678[...]: node "example.zip" with invalid type "irregular" tree 12345678[...]: node "example.zip" with invalid type "irregular"
``` ```
Repairing the affected snapshots requires upgrading to restic 0.17.2 and then To repair affected snapshots, upgrade to restic 0.17.2 and run:
manually running `restic repair snapshots --forget`. This will remove the
`irregular` files from the snapshots. ```
restic repair snapshots --forget
```
This will remove the `irregular` files from the snapshots.
https://github.com/restic/restic/pull/5057 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 https://forum.restic.net/t/errors-found-by-check-1-invalid-type-irregular-2-ciphertext-verification-failed/8447/2