From 7a5d29ce24d1545e99edbe2aa46a2f4eb84c74e9 Mon Sep 17 00:00:00 2001 From: Michael Eischer Date: Wed, 24 Aug 2022 21:13:14 +0200 Subject: [PATCH] Further changelog polishing --- changelog/unreleased/issue-21 | 5 +++-- changelog/unreleased/issue-3295 | 4 ++-- changelog/unreleased/pull-3475 | 3 ++- changelog/unreleased/pull-3680 | 1 + changelog/unreleased/pull-3772 | 3 ++- 5 files changed, 10 insertions(+), 6 deletions(-) diff --git a/changelog/unreleased/issue-21 b/changelog/unreleased/issue-21 index 412448b4f..a105d8ecd 100644 --- a/changelog/unreleased/issue-21 +++ b/changelog/unreleased/issue-21 @@ -7,8 +7,9 @@ that the repository cannot be read by restic versions prior to 0.14.0. You can configure whether data is compressed with the option `--compression`. It can be set to `auto` (the default, which will compress very fast), `max` (which will trade backup speed and CPU usage for better compression), or `off` (which -disables compression). Each setting is only applied for the single run of restic. -The option can also be set via the environment variable `RESTIC_COMPRESSION`. +disables compression). Each setting is only applied for the current run of restic +and does *not* apply to future runs. The option can also be set via the +environment variable `RESTIC_COMPRESSION`. To upgrade in place run `migrate upgrade_repo_v2` followed by `prune`. See the documentation for more details. The migration checks the repository integrity diff --git a/changelog/unreleased/issue-3295 b/changelog/unreleased/issue-3295 index 511c3b9d8..1a6b72724 100644 --- a/changelog/unreleased/issue-3295 +++ b/changelog/unreleased/issue-3295 @@ -2,8 +2,8 @@ Change: Deprecate `check --check-unused` and add further checks Since restic 0.12.0, it is expected to still have unused blobs after running `prune`. This made the `--check-unused` option of the `check` command rather -useless and tended to confuse users. This option has now been deprecated and -is now ignored. +useless and tended to confuse users. This option has been deprecated and is +now ignored. The `check` command now also warns if a repository is using either the legacy S3 layout or mixed pack files with both tree and data blobs. The latter is diff --git a/changelog/unreleased/pull-3475 b/changelog/unreleased/pull-3475 index 99a037778..9932ae632 100644 --- a/changelog/unreleased/pull-3475 +++ b/changelog/unreleased/pull-3475 @@ -3,6 +3,7 @@ Enhancement: Allow limiting IO concurrency for local and SFTP backend Restic did not support limiting the IO concurrency / number of connections for accessing repositories stored using the local or SFTP backends. The number of connections is now limited as for other backends, and can be configured via the -the `-o local.connections=2` and `-o sftp.connections=5` options. +the `-o local.connections=2` and `-o sftp.connections=5` options. This ensures +that restic does not overwhelm the backend with concurrent IO operations. https://github.com/restic/restic/pull/3475 diff --git a/changelog/unreleased/pull-3680 b/changelog/unreleased/pull-3680 index e4f673fcf..c86624a2b 100644 --- a/changelog/unreleased/pull-3680 +++ b/changelog/unreleased/pull-3680 @@ -5,3 +5,4 @@ features we're dropping support for Go 1.14, which means that restic now requires at least Go 1.15 to build. https://github.com/restic/restic/issues/3680 +https://github.com/restic/restic/issues/3883 diff --git a/changelog/unreleased/pull-3772 b/changelog/unreleased/pull-3772 index 184fa9741..858832b3f 100644 --- a/changelog/unreleased/pull-3772 +++ b/changelog/unreleased/pull-3772 @@ -1,7 +1,7 @@ Bugfix: Correctly rebuild index for legacy repositories After running `rebuild-index` on a legacy repository containing mixed pack -files (that is, pack files with store both metadata and file data), `check` +files (that is, pack files which store both metadata and file data), `check` printed warnings like `pack 12345678 contained in several indexes: ...`. This warning was not critical, but has now nonetheless been fixed by properly handling mixed pack files while rebuilding the index. @@ -10,4 +10,5 @@ Running `prune` for such legacy repositories will also fix the warning by reorganizing the pack files which caused it. https://github.com/restic/restic/pull/3772 +https://github.com/restic/restic/pull/3884 https://forum.restic.net/t/5044/13