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

doc: Polish changelogs

Browse source
This commit is contained in:
Leo R. Lundgren 2023-10-23 20:45:15 +02:00
parent 85abceb99c
commit 6d19e0260d
2 changed files with 22 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

25
changelog/unreleased/issue-4523
View file

@ -1,17 +1,22 @@
Bugfix: Update zstd library to fix possible data corruption at max. compression 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 In restic 0.16.0, backups where the compression level was set to `max` (using
corruption due to a bug in the library used for compressing data. Please note `--compression max`) could in rare and very specific circumstances result in
that the "auto" compression level (used by default) is not affected! data corruption due to a bug in the library used for compressing data.
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.
Restic now uses the latest version of the library used to compress data, which 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/issues/4523
https://github.com/restic/restic/pull/4530 https://github.com/restic/restic/pull/4530

13
changelog/unreleased/pull-4480
View file

@ -1,10 +1,11 @@
Enhancement: Allow setting REST password and username via environment variables Enhancement: Allow setting REST password and username via environment variables
Previously, it was only possible to specify the REST server username and Previously, it was only possible to specify the REST-server username and
password in the repository URL, or using the `--repository-file` option. This password in the repository URL, or by using the `--repository-file` option.
meant it was not possible to use authentication in contexts where the 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 repository URL is stored in publicly accessible way.
the username and password using the `RESTIC_REST_USERNAME` and
`RESTIC_REST_PASSWORD` variables. 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 https://github.com/restic/restic/pull/4480