Merge branch 'patch-release'

2026-08-14 01:23:18 +00:00 · 2025-09-21 21:20:56 +02:00
parent 4871390a81 39a737fe14
commit f091e6aed0
12 changed files with 135 additions and 35 deletions
@@ -1,14 +0,0 @@
-Bugfix: Correctly handle `backup --stdin-filename` with directories
-
-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,
-`--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.
-
-https://github.com/restic/restic/issues/5324
-https://github.com/restic/restic/pull/5356
@@ -1,7 +0,0 @@
-Bugfix: Correctly handle `RESTIC_HOST` in `forget` command
-
-The `forget` command did not use the host name from the `RESTIC_HOST`
-environment variable. This has been fixed.
-
-https://github.com/restic/restic/issues/5325
-https://github.com/restic/restic/pull/5327
@@ -1,7 +0,0 @@
-Bugfix: Ignore "chmod not supported" errors when writing files
-
-Restic 0.18.0 introduced a bug that caused "chmod xxx: operation not supported"
-errors to appear when writing to a local file repository that did not support
-chmod (like CIFS or WebDAV mounted via FUSE). Restic now ignores those errors.
-
-https://github.com/restic/restic/issues/5342
@@ -1,7 +0,0 @@
-Bugfix: Ignore EOPNOTSUPP as an error for xattr
-
-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.
-
-https://github.com/restic/restic/issues/5344
@@ -1,8 +0,0 @@
-Bugfix: do not retry if 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.
-
-https://github.com/restic/restic/issues/5429
-https://github.com/restic/restic/pull/5452
@@ -1,27 +0,0 @@
-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.
-
-This could result in an error output like the following:
-```
-Load(<data/34567890ab>, 33918928, 0) returned error, retrying after 871.35598ms: readFull: unexpected EOF
-Load(<data/34567890ab>, 33918928, 0) operation successful after 1 retries
-check successful on second attempt, original error pack 34567890ab[...] contains 6 errors: [blob 12345678[...]: decrypting blob <data/12345678> from 34567890 failed: ciphertext verification failed ...]
-[...]
-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
-`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.
-
-https://github.com/restic/restic/issues/5467
-https://github.com/restic/restic/pull/5495
@@ -1,8 +0,0 @@
-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.
-
-https://github.com/restic/restic/pull/5421