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

Tweak wording

Browse source 
Co-authored-by: rawtaz <rawtaz@users.noreply.github.com>
This commit is contained in:
Michael Eischer 2024-10-22 20:00:39 +02:00
parent 2ce485063f
commit d8d955e0aa
3 changed files with 6 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
changelog/unreleased/issue-5050
View file

@ -1,7 +1,7 @@
Bugfix: Return 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 when it failed 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. to open or lock the repository. This issue has now 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

2
changelog/unreleased/issue-5063
View file

@ -5,7 +5,7 @@ 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 snapshot. This could result in errors if files were removed during the backup
process. process.
This issue has been resolved. This issue has now been resolved.
https://github.com/restic/restic/issues/5063 https://github.com/restic/restic/issues/5063
https://github.com/restic/restic/pull/5097 https://github.com/restic/restic/pull/5097

7
changelog/unreleased/pull-5057
View file

@ -1,8 +1,8 @@
Bugfix: Exclude irregular files from backups Bugfix: Exclude irregular files from backups
Since restic 0.17.1, files with the type irregular could mistakenly be included 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 in snapshots, especially when backing up special file types on Windows that
restic cannot process. This issue has been fixed. restic cannot process. This issue has now been fixed.
Previously, this bug caused the `check` command to report errors like the Previously, this bug caused the `check` command to report errors like the
following one: following one:
@ -17,7 +17,8 @@ To repair affected snapshots, upgrade to restic 0.17.2 and run:
restic repair snapshots --forget restic repair snapshots --forget
``` ```
This will remove the `irregular` files from the snapshots. This will remove the `irregular` files from the snapshots (creating
a new snapshot ID for each of the affected 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