From 6d19e0260dd2c59e92b2ad611954c03dfc674f7a Mon Sep 17 00:00:00 2001 From: "Leo R. Lundgren" Date: Mon, 23 Oct 2023 20:45:15 +0200 Subject: [PATCH] doc: Polish changelogs --- changelog/unreleased/issue-4523 | 25 +++++++++++++++---------- changelog/unreleased/pull-4480 | 13 +++++++------ 2 files changed, 22 insertions(+), 16 deletions(-) diff --git a/changelog/unreleased/issue-4523 b/changelog/unreleased/issue-4523 index 3dd4a536f..e246cfe28 100644 --- a/changelog/unreleased/issue-4523 +++ b/changelog/unreleased/issue-4523 @@ -1,17 +1,22 @@ Bugfix: Update zstd library to fix possible data corruption at max. compression -In restic 0.16.0, backups using maximum compression could result in data -corruption due to a bug in the library used for compressing data. Please note -that the "auto" compression level (used by default) is not affected! - -To check a repository for data corruption, run `restic check --read-data`. This -will download and verify the whole repository. If the `check` command detects -data corruption, follow the suggested steps. To simplify the repository repair -and minimize data loss, we've also added an experimental `repair packs` command -that salvages all valid data from the affected pack files. +In restic 0.16.0, 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 now uses the latest version of the library used to compress data, which -includes a fix for the data corruption issue. +includes a fix for this issue. 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 were very 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. + +To simplify any needed repository repair and minimize data loss, there is also +a new and experimental `repair packs` command that salvages all valid data from +the affected pack files (see `restic help repair packs` for more information). https://github.com/restic/restic/issues/4523 https://github.com/restic/restic/pull/4530 diff --git a/changelog/unreleased/pull-4480 b/changelog/unreleased/pull-4480 index ec5e68761..2075fe21d 100644 --- a/changelog/unreleased/pull-4480 +++ b/changelog/unreleased/pull-4480 @@ -1,10 +1,11 @@ Enhancement: Allow setting REST password and username via environment variables -Previously, it was only possible to specify the REST server username and -password in the repository URL, or using the `--repository-file` option. This -meant it was not possible to use authentication in contexts where the -repository URL is stored in publicly accessible way. Restic now allows setting -the username and password using the `RESTIC_REST_USERNAME` and -`RESTIC_REST_PASSWORD` variables. +Previously, it was only possible to specify the REST-server username and +password in the repository URL, or by using the `--repository-file` option. +This meant it was not possible to use authentication in contexts where the +repository URL is stored in publicly accessible way. + +Restic now allows setting the username and password using the +`RESTIC_REST_USERNAME` and `RESTIC_REST_PASSWORD` variables. https://github.com/restic/restic/pull/4480