TheArchive/restic
1
0
Fork 0
mirror of https://github.com/restic/restic.git synced 2025-12-13 15:13:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #5509 from restic/polish-changelogs

Browse Source 
slightly polish changelogs
This commit is contained in:
Michael Eischer
2025-09-17 20:37:46 +02:00
committed by GitHub
parent 4940e330c0 9ef8e13102
commit b12a638322
6 changed files with 23 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
changelog/unreleased/issue-5324
View File

@@ -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 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: `--stdin-filename /foo/bar` resulted in the following error:
``` ```
Fatal: unable to save snapshot: open /foo: no such file or directory 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/issues/5324
https://github.com/restic/restic/pull/5356 https://github.com/restic/restic/pull/5356

4
changelog/unreleased/issue-5325
View File

@@ -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` 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/issues/5325
https://github.com/restic/restic/pull/5327 https://github.com/restic/restic/pull/5327

8
changelog/unreleased/issue-5344
View File

@@ -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 Restic 0.18.0 added extended attribute support for NetBSD 10+, but not all
filesystems support xattrs. Other BSD systems can likewise return NetBSD filesystems support extended attributes. Other BSD systems can
EOPNOTSUPP, so restic now simply ignores EOPNOTSUPP errors for xattrs. likewise return EOPNOTSUPP, so restic now ignores these errors.
https://github.com/restic/restic/issues/5344 https://github.com/restic/restic/issues/5344

8
changelog/unreleased/issue-5429
View File

@@ -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 When rest-server returns a `507 Insufficient Storage` error, it indicates
capacity is available at the server. Restic now no longer retries uploads that no more storage capacity is available. Restic now correctly stops
in this case. retrying uploads in this case.
https://github.com/restic/restic/issues/5429 https://github.com/restic/restic/issues/5429
https://github.com/restic/restic/pull/5452 https://github.com/restic/restic/pull/5452

15
changelog/unreleased/issue-5467
View File

@@ -1,8 +1,8 @@
Bugfix: Improve handling of download retries in `check` command Bugfix: Improve handling of download retries in `check` command
In very rare cases, the `check` command could unnecessarily report a In very rare cases, the `check` command could unnecessarily report repository
repository damage if the backend returns incomplete, corrupted data on damage if the backend returned incomplete, corrupted data on the first download
the first download try which is resolved by a download retry. try which is afterwards resolved by a download retry.
This could result in an error output like the following: 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 Fatal: repository contains errors
``` ```
This fix only applies to a very specific case. The required condition is This fix only applies to a very specific case where the log shows
a `operation successful after 1 retries` error in the log, later followed by `operation successful after 1 retries` followed by a
a `check successful on second attempt, original error` error that only reports `check successful on second attempt, original error` that only reports
`ciphertext verification failed` errors in the pack file. If any other errors `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 are reported in the pack file, then the repository still has to be considered
as damaged. as damaged.
Now, only the check result of the last download retry is reported as Now, only the check result of the last download retry is reported as intended.
intended.
https://github.com/restic/restic/issues/5467 https://github.com/restic/restic/issues/5467
https://github.com/restic/restic/pull/5495 https://github.com/restic/restic/pull/5495

7
changelog/unreleased/pull-5421
View File

@@ -1,8 +1,7 @@
Bugfix: Fix rare crash if directory is removed during backup 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 In restic 0.18.0, the `backup` command could crash if a directory was removed
inbetween reading its metadata and listing its directory content. between reading its metadata and listing its directory content. This has now
been fixed.
This has been fixed.
https://github.com/restic/restic/pull/5421 https://github.com/restic/restic/pull/5421