mirror of
https://github.com/octoleo/restic.git
synced 2024-12-23 03:18:55 +00:00
ce14df303b
This removes the requirement on `restic self-update --output` to point to a path of an existing file, to overwrite. In case the specified path does exist we still want to verify that it's a regular file, rather than a directory or a device, which gets overwritten. We also want to verify that a path to a new file exists within an existing directory. The alternative being running into that issue after the actual download, etc has completed. While at it I also replace `errors.Errorf` with the more appropriately verbose `errors.Fatalf`. Resolves #2491
10 lines
396 B
Plaintext
10 lines
396 B
Plaintext
Bugfix: Don't require `self-update --output` placeholder file
|
|
|
|
`restic self-update --output /path/to/new-restic` used to require that
|
|
new-restic was an existing file, to be overwritten. Now it's possible
|
|
to download an updated restic binary to a new path, without first
|
|
having to create a placeholder file.
|
|
|
|
https://github.com/restic/restic/issues/2491
|
|
https://github.com/restic/restic/pull/2937
|