From 9e3703ded525b2d6755fa385b8f82b6f785d1392 Mon Sep 17 00:00:00 2001 From: Michael Eischer Date: Mon, 12 Feb 2024 20:39:31 +0100 Subject: [PATCH] remove changelogs that are already included in restic 0.16.4 --- changelog/unreleased/issue-4529 | 18 ------------------ changelog/unreleased/issue-4677 | 19 ------------------- 2 files changed, 37 deletions(-) delete mode 100644 changelog/unreleased/issue-4529 delete mode 100644 changelog/unreleased/issue-4677 diff --git a/changelog/unreleased/issue-4529 b/changelog/unreleased/issue-4529 deleted file mode 100644 index fed726d2d..000000000 --- a/changelog/unreleased/issue-4529 +++ /dev/null @@ -1,18 +0,0 @@ -Enhancement: Add extra verification of data integrity before upload - -Hardware issues, or a bug in restic or its dependencies, could previously cause -corruption in the files restic created and stored in the repository. Detecting -such corruption previously required explicitly running the `check --read-data` -or `check --read-data-subset` commands. - -To further ensure data integrity, even in the case of hardware issues or -software bugs, restic now performs additional verification of the files about -to be uploaded to the repository. - -These extra checks will increase CPU usage during backups. They can therefore, -if absolutely necessary, be disabled using the `--no-extra-verify` global -option. Please note that this should be combined with more active checking -using the previously mentioned check commands. - -https://github.com/restic/restic/issues/4529 -https://github.com/restic/restic/pull/4681 diff --git a/changelog/unreleased/issue-4677 b/changelog/unreleased/issue-4677 deleted file mode 100644 index 8fa6cf65b..000000000 --- a/changelog/unreleased/issue-4677 +++ /dev/null @@ -1,19 +0,0 @@ -Bugfix: Downgrade zstd library to fix rare data corruption at max. compression - -In restic 0.16.3, backups where the compression level was set to `max` (using -`--compression max`) could in rare and very specific circumstances result in -data corruption due to a bug in the library used for compressing data. Restic -0.16.1 and 0.16.2 were not affected. - -Restic now uses the previous version of the library used to compress data, the -same version used by restic 0.16.2. Please note that the `auto` compression -level (which restic uses by default) was never affected, and even if you used -`max` compression, chances of being affected by this issue are small. - -To check a repository for any corruption, run `restic check --read-data`. This -will download and verify the whole repository and can be used at any time to -completely verify the integrity of a repository. If the `check` command detects -anomalies, follow the suggested steps. - -https://github.com/restic/restic/issues/4677 -https://github.com/restic/restic/pull/4679