diff --git a/changelog/unreleased/issue-5324 b/changelog/unreleased/issue-5324 index 0f5ff77e4..2143c568e 100644 --- a/changelog/unreleased/issue-5324 +++ b/changelog/unreleased/issue-5324 @@ -1,14 +1,14 @@ -Bugfix: Correctly handle `backup --stdin-filename` with directories +Bugfix: Correctly handle `backup --stdin-filename` with directory paths In restic 0.18.0, the `backup` command failed if a filename that includes -a least a directory was passed to `--stdin-filename`. For example, +at least a directory was passed to `--stdin-filename`. For example, `--stdin-filename /foo/bar` resulted in the following error: ``` Fatal: unable to save snapshot: open /foo: no such file or directory ``` -This has been fixed now. +This has now been fixed. https://github.com/restic/restic/issues/5324 https://github.com/restic/restic/pull/5356 diff --git a/changelog/unreleased/issue-5325 b/changelog/unreleased/issue-5325 index 883391a0a..8c464e9ca 100644 --- a/changelog/unreleased/issue-5325 +++ b/changelog/unreleased/issue-5325 @@ -1,7 +1,7 @@ -Bugfix: Correctly handle `RESTIC_HOST` in `forget` command +Bugfix: Accept `RESTIC_HOST` environment variable in `forget` command The `forget` command did not use the host name from the `RESTIC_HOST` -environment variable. This has been fixed. +environment variable when filtering snapshots. This has now been fixed. https://github.com/restic/restic/issues/5325 https://github.com/restic/restic/pull/5327 diff --git a/changelog/unreleased/issue-5344 b/changelog/unreleased/issue-5344 index 38119d0ec..d4b1bc889 100644 --- a/changelog/unreleased/issue-5344 +++ b/changelog/unreleased/issue-5344 @@ -1,7 +1,7 @@ -Bugfix: Ignore EOPNOTSUPP as an error for xattr +Bugfix: Ignore EOPNOTSUPP errors for extended attributes -Restic 0.18.0 added xattr support for NetBSD 10+, but not all NetBSD -filesystems support xattrs. Other BSD systems can likewise return -EOPNOTSUPP, so restic now simply ignores EOPNOTSUPP errors for xattrs. +Restic 0.18.0 added extended attribute support for NetBSD 10+, but not all +NetBSD filesystems support extended attributes. Other BSD systems can +likewise return EOPNOTSUPP, so restic now ignores these errors. https://github.com/restic/restic/issues/5344 diff --git a/changelog/unreleased/issue-5429 b/changelog/unreleased/issue-5429 index e8e7ca513..941953a35 100644 --- a/changelog/unreleased/issue-5429 +++ b/changelog/unreleased/issue-5429 @@ -1,8 +1,8 @@ -Bugfix: do not retry if rest-server runs out of space +Bugfix: Stop retrying uploads when rest-server runs out of space -Rest-server return error `507 Insufficient Storage` if no more storage -capacity is available at the server. Restic now no longer retries uploads -in this case. +When rest-server returns a `507 Insufficient Storage` error, it indicates +that no more storage capacity is available. Restic now correctly stops +retrying uploads in this case. https://github.com/restic/restic/issues/5429 https://github.com/restic/restic/pull/5452 diff --git a/changelog/unreleased/issue-5467 b/changelog/unreleased/issue-5467 index 4b50fc857..1f746e154 100644 --- a/changelog/unreleased/issue-5467 +++ b/changelog/unreleased/issue-5467 @@ -1,8 +1,8 @@ Bugfix: Improve handling of download retries in `check` command -In very rare cases, the `check` command could unnecessarily report a -repository damage if the backend returns incomplete, corrupted data on -the first download try which is resolved by a download retry. +In very rare cases, the `check` command could unnecessarily report repository +damage if the backend returned incomplete, corrupted data on the first download +try which is afterwards resolved by a download retry. This could result in an error output like the following: ``` @@ -13,15 +13,14 @@ check successful on second attempt, original error pack 34567890ab[...] contains Fatal: repository contains errors ``` -This fix only applies to a very specific case. The required condition is -a `operation successful after 1 retries` error in the log, later followed by -a `check successful on second attempt, original error` error that only reports +This fix only applies to a very specific case where the log shows +`operation successful after 1 retries` followed by a +`check successful on second attempt, original error` that only reports `ciphertext verification failed` errors in the pack file. If any other errors are reported in the pack file, then the repository still has to be considered as damaged. -Now, only the check result of the last download retry is reported as -intended. +Now, only the check result of the last download retry is reported as intended. https://github.com/restic/restic/issues/5467 https://github.com/restic/restic/pull/5495 diff --git a/changelog/unreleased/pull-5421 b/changelog/unreleased/pull-5421 index 3a76d4fcd..0eb49fc44 100644 --- a/changelog/unreleased/pull-5421 +++ b/changelog/unreleased/pull-5421 @@ -1,8 +1,7 @@ Bugfix: Fix rare crash if directory is removed during backup -In restic 0.18.0, the `backup` command could crash if a directory is removed -inbetween reading its metadata and listing its directory content. - -This has been fixed. +In restic 0.18.0, the `backup` command could crash if a directory was removed +between reading its metadata and listing its directory content. This has now +been fixed. https://github.com/restic/restic/pull/5421