We use restic on a set of Windows servers, running daily automatic updates using self-update.
Since the release of 0.15, the previous version (on all servers) stopped working.
We do restic self-update --output restic-next.exe and it suddenly fails everywhere with:
writing restic to C:\Path\To\Restic\restic-next.exe
find latest release of restic at GitHub
latest version is 0.15.0
GPG signature verification succeeded
Fatal: unable to update restic: unable to rename target file: rename C:\Path\To\Restic\restic-next.exe C:\Path\To\Restic\restic-next.exe.bak: The system cannot find the file specified.
The suggested workaround worked when I tested it. We can adopt that I think.
I comes with a side-effect that it leaves a restic-next.exe.bak behind (a copy of the dummy file), but it’s not a real problem.